| 2 | Approval of the agenda | |
|---|---|---|
| R4-2004831 | Agenda | RAN4 Chairman |
| R4-2004832 | RAN4#94 Meeting Report | ETSI |
| 3 | Letters / reports from other groups / meetings | |
| R4-2003360 | Reply LS on clarification of CLI resource configuration | RAN1 |
| R4-2003361 | LS on CLI measurement and reporting | RAN1 |
| R4-2003362 | LS on SSB index and candidate SSB index for NR-U | RAN1 |
| R4-2003363 | LS on power control for NR-DC | RAN2 |
| R4-2003364 | LS on Sidelink UE capability for (NG)EN-DC and NE-DC | RAN2 |
| R4-2003365 | Reply LS on CGI reading with autonomous gaps | RAN2 |
| R4-2003366 | LS to RAN4 on measurement range and granularity | RAN2 |
| R4-2003367 | LS to RAN1 on T_delta in IAB | RAN2 |
| R4-2003368 | LS on dropping measurement results due to LBT delays | RAN2 |
| R4-2003369 | Clarification of UE requirements for early measurement performance and reporting | RAN2 |
| R4-2003370 | Guidelines for UE capability definitions | RAN2 |
| R4-2003371 | LS on dormant BWP configuration and related operation | RAN2 |
| R4-2003372 | LS to RAN4 on RRM relaxation in power saving | RAN2 |
| R4-2003373 | LS on parameters of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-23 | RAN |
| R4-2003374 | LS on publication of TS.51 V1.0 | GSMA TSG IoTOTA group |
| R4-2004830 | LS on Rel-16 RAN1 UE features lists for LTE | ETSI |
| 4.1 | NE-DC, NGEN-DC, and NR-NR DC Maintenance [NR_newRAT-Core] | |
| R4-2003172 | Discussion on how to handle the NE-DC band combinations | Samsung |
| R4-2003173 | Draft CR for 38.101-3 to introduce new inter-band NE-DC band combinations including FR2 | Samsung, SK telecom |
| R4-2003174 | Draft CR for 38.101-3 to introduce new inter-band NE-DC band combinations within FR1 | Samsung, SK telecom |
| 4.2 | System Parameters Maintenance [NR_newRAT-Core] | |
| R4-2003729 | Proposal on adding 30KHz SCS for n40 SSB | Huawei, HiSilicon |
| R4-2003730 | TS38.101-1 draft CR: adding 30KHz SSB SCS for n40 | Huawei, HiSilicon |
| R4-2003731 | TS38.101-1 draft CR: adding 30KHz SSB SCS for n50 | Huawei, HiSilicon |
| R4-2003732 | TS38.101-1 draft CR: adding 30KHz SSB SCS for n38 | Huawei, HiSilicon |
| R4-2003780 | Consideration on 30KHz SCS for band n40 SSB | ZTE Corporation |
| R4-2003859 | Addition of 30k SSB SCS for Band n34, n39 and n50 | Ericsson |
| R4-2003860 | Addition of 30k SSB SCS for Band n34, n39 and n50 | Ericsson |
| R4-2003861 | Addition of 30k SSB SCS for Band n38 | Ericsson |
| R4-2003862 | Addition of 30k SSB SCS for Band n38 | Ericsson |
| R4-2003955 | Release independence support for adding new channel bandwidth to existing operating bands | ZTE Wistron Telecom AB |
| R4-2003956 | draftCR to TS 38.307 Supporting new channel bandwidth added to existing operating bands in a release independent manner | ZTE Wistron Telecom AB |
| R4-2004772 | CR for 38.101-1 channel space for CA_Rel15 | Huawei, HiSilicon |
| R4-2004773 | CR for 38.101-1 channel space for CA_Rel16 | Huawei, HiSilicon |
| R4-2004774 | CR for 38.101-2 channel space for CA_Rel15 | Huawei, HiSilicon |
| R4-2004775 | CR for 38.101-2 channel space for CA_Rel16 | Huawei, HiSilicon |
| R4-2004776 | On channel space for CA | Huawei, HiSilicon |
| 4.4 | UE RF requirements maintenance [NR_newRAT] | |
| R4-2003241 | More on necessity of signaling supported NS values | NTT DOCOMO, INC. |
| R4-2003243 | [Draft] LS on reporting newly introduced NS(s) for an existing band | NTT DOCOMO, INC. |
| R4-2003906 | Further on NS value report | OPPO |
| 4.4.1.1 | Maintenance for bands and band combinations in 38.101-1 | |
| R4-2004998 | Usage of n77 in US C-band | Nokia |
| 4.4.1.2 | Maintenance for bands and band combinations in 38.101-2 | |
| R4-2003525 | Draft CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications | MediaTek Inc. |
| R4-2003594 | Draft CR to TS 38.101-2 on corrections to intra-band contiguous CA band for FR2 (Rel-15) | ZTE Corporation |
| R4-2003863 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| 4.4.1.3 | Maintenance for combinations in 38.101-3 [NR_newRAT-Core] | |
| R4-2003278 | Draft CR for TS38.101-3, Aligned IE RF-Parameters name of maxUplinkDutyCycle with RAN2 | CATT |
| R4-2003864 | Removal of contradicting fall-back specification for intra-band non-contigous CA/DC | Ericsson |
| R4-2004741 | CR for 38.101-3 Correction on EN-DC synchronous carriers (Rel-15) | Huawei, HiSilicon |
| R4-2004742 | CR for 38.101-3 Correction on EN-DC synchronous carriers (Rel-16) | Huawei, HiSilicon |
| R4-2004929 | Draft CR for TR37.863-01-01: TP for missing MSD due to UL harmonic and cross band isolation for band combinations | MediaTek Inc. |
| R4-2004930 | Draft CR for TS 38.101-3: Missing MSD due to cross band isolation | MediaTek Inc. |
| R4-2004931 | Draft CR for TS 38.101-3: MSD due to UL harmonic | MediaTek Inc. |
| 4.4.2 | [FR1] Maintenance for general requirements in 38.101-1 [NR_newRAT-Core] | |
| R4-2003788 | Draft CR to TS38.101-1_Replace CBW with symbols defined in the specification | ZTE Corporation |
| 4.4.2.1 | Power class related to UL MIMO and other related req. (MPR, SEM, etc) [NR_newRAT-Core] | |
| R4-2003249 | Clarficiation of PC2 UL-MIMO in Rel-15 | LG Electronics Polska |
| R4-2003536 | Discussion on Tx Diversity and Power Class Issues for Rel-15 NR | Samsung |
| R4-2003865 | Correction of transmitter characteristics for UL-MIMO: powerclass 2 and fallback | Ericsson |
| R4-2003866 | Remove power-class ambiguity for UL-MIMO PC2 capable UE configured for EN-DC | Ericsson |
| R4-2003903 | Further on UL MIMO PC2 fallback | OPPO |
| R4-2003904 | LS on Rel-15 power class | OPPO |
| R4-2004045 | CR to 38.101-1: UL MIMO MPR reference table (R15) | vivo |
| R4-2004046 | CR to 38.101-1: UL MIMO MPR reference table (R16) | vivo |
| R4-2004047 | On R15 UL MIMO MOP requirements | vivo |
| R4-2004048 | Draft LS on clarification of ENDC power class in R15 | vivo |
| R4-2004049 | Draft Reply LS on further discussion of the testability of FR1 Tx diversity | vivo |
| R4-2004211 | Impact of transparent TX diversity in Rel-15 on conformance testing | Keysight Technologies UK Ltd |
| R4-2004691 | Contribution to Tx Diversity and UL MIMO | Apple Inc. |
| R4-2004732 | On Rel-15 PC2 power class | Huawei, HiSilicon |
| R4-2004733 | On Rel-15 PC2 unwanted emissions and MPR requirement | Huawei, HiSilicon |
| R4-2004735 | Draft CR on Rel-15 UL MIMO requirements | Huawei, HiSilicon |
| R4-2004736 | On EN-DC power class | Huawei, HiSilicon |
| R4-2004821 | Summary of issues related to power class ambiguities and tx div | Qualcomm Incorporated |
| R4-2004959 | Proposal on power class 2 UE requirements | CMCC |
| R4-2004960 | Draft CR for UL MIMO requirements | CMCC |
| R4-2004976 | Tx diversity and power class ambiguity handling in Rel-15 | Qualcomm Incorporated |
| 4.4.2.2 | Other Tx requirements [NR_newRAT-Core] | |
| R4-2003867 | Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification | Ericsson |
| R4-2003868 | Corrections to sub-block size and guard band | Ericsson |
| R4-2004722 | PC2 fallback and redundant power backoff | Qualcomm Incorporated |
| R4-2004734 | On UL MIMO Tx EVM requirement | Huawei, HiSilicon |
| R4-2004739 | CR for TS 38.101-1 correction of delta SRS (Rel-15) | Huawei, HiSilicon |
| R4-2004740 | CR for TS 38.101-1 correction of delta SRS (Rel-16) | Huawei, HiSilicon |
| R4-2004760 | CR for intra-band CA DL Rx requirement_Rel-15 | Huawei, HiSilicon |
| R4-2004761 | CR for intra-band CA DL Rx requirement_Rel-16 | Huawei, HiSilicon |
| R4-2004791 | EVM Definitions for Antenna Ports and MIMO Layers | Motorola Mobility Germany GmbH |
| R4-2004866 | FR1 TX EVM test condition correction for ULMIMO | Qualcomm Incorporated |
| R4-2004867 | dCR to 38.101-1: Revision to ULMIMO EVM spec | Qualcomm Incorporated |
| 4.4.2.3 | Maintenance for Receiver characteristics [NR_newRAT-Core] | |
| R4-2003326 | Consideration on PDCCH testability issue with ACS | Anritsu Corp. |
| R4-2003327 | Testability issue with OoBB for FR1 EN-DC UE (2) | Anritsu Corp. |
| R4-2003328 | Draft CR to out-of-band blocking for DC in FR1 | Anritsu Corp., Rohde & Schwarz |
| R4-2003526 | NR UE receiver ACS tests RMC configuration | MediaTek Inc. |
| R4-2003663 | Draft CR to TS 38.101-1: corrections on ACS for intra-band contiguous CA | Xiaomi |
| R4-2003664 | Draft CR to TS 38.101-3: corrections on ACS for intra-band contiguous EN-DC | Xiaomi |
| R4-2004141 | Draft CR for 38.101-1 to remove the NR CA configuration for REFSENS exception due to cross band isolation for CA | Huawei, HiSilicon |
| R4-2004142 | Draft CR for 38.101-1 to simplify the REFSENS for inter band CA with SDL | Huawei, HiSilicon |
| R4-2004143 | Draft CR for 38.101-1 to add requirements for inter-band CA with two UL bands | Huawei, HiSilicon |
| 4.4.3 | [FR2] Maintenance for general requirements in 38.101-2 [NR_newRAT-Core] | |
| R4-2004868 | Reply to LS R5-199424 on FR2 Multiband Relaxations | Qualcomm Incorporated |
| R4-2005002 | Correction for REL16 FR2 contiguous intraband CA configuration table | Nokia, Nokia Shanghai Bell |
| R4-2005003 | draft CR Correction for REL16 FR2 contiguous intraband CA configuration table | Nokia, Qualcomm, Inc, Ericsson |
| 4.4.3.1 | Regulatory Tx/Rx spurious emission limits handling [NR_newRAT-Core] | |
| R4-2003248 | WRC resolution for n257 and n258 | NTT DOCOMO, INC. |
| R4-2004681 | WRC-19 resolutions and impact to NR bands | Apple Inc. |
| R4-2004767 | On FR2 EESS protection emission requirement | Huawei, HiSilicon |
| R4-2004876 | dCR to 38.101-2: NS_202 update after changes to EU regulations | Qualcomm Incorporated |
| R4-2004878 | Incorporating WRC19 resolutions into FR2 specifications | Qualcomm Incorporated |
| R4-2004879 | dCR to 38.101-2: Introduction of NS flags and A-MPR from WRC19 Resolutions | Qualcomm Incorporated |
| R4-2005000 | Required updates to UE requirements due to WRC-19 decisions | Nokia, Nokia Shanghai Bell |
| 4.4.3.2 | Maintenance for Transmitter characteristics [NR_newRAT-Core] | |
| R4-2003329 | Comparison of ACLR MBW definition with regulation in Japan | Anritsu Corp., KDDI Corp., SoftBank Corp, NTT DOCOMO Inc.. |
| R4-2003337 | Correction on transmission gap for FR2 relative power tolerance | Ericsson |
| R4-2003527 | Draft CR for TS 38.101-2: Correction for configured maximum output power | MediaTek Inc. |
| R4-2003869 | Correction of Pcmax for CA | Ericsson |
| R4-2003905 | On max reference power in UL duty cycle capability | OPPO |
| R4-2004682 | Clarification for the definition of the UL duty cycle | Apple Inc. |
| R4-2004683 | [draft] LS on clarification for the definition of the UL duty cycle | Apple Inc. |
| R4-2004707 | On FR2 64QAM UL RMC | Apple Inc. |
| R4-2004708 | Draft CR to 38.101-2 on correction of FR2 64QAM UL RMC | Apple Inc. |
| R4-2004709 | Draft CR to 38.101-2 on correction of reference point for beam correspondence side conditions | Apple Inc. |
| R4-2004758 | CR for for reference maximum transmission power for maxUplinkdutyCycle_Rel-15 | Huawei, HiSilicon |
| R4-2004759 | CR for for reference maximum transmission power for maxUplinkdutyCycle_Rel-16 | Huawei, HiSilicon |
| R4-2004762 | CR for intra-band CA DL Rx requirement-FR2_Rel-15 | Huawei, HiSilicon |
| R4-2004763 | CR for intra-band CA DL Rx requirement-FR2_Rel-16 | Huawei, HiSilicon |
| R4-2004764 | CR for modified MPR_Rel-15 | Huawei, HiSilicon |
| R4-2004765 | CR for modified MPR_Rel-15 | Huawei, HiSilicon |
| R4-2004820 | on PTRS configuration for UL RMC | Huawei, HiSilicon |
| R4-2004822 | CR on PTRS configuration for UL RMC | Huawei, HiSilicon |
| R4-2004974 | Draft CR on Pcmax correction for CA | Qualcomm Incorporated |
| R4-2004975 | How power control works and why re-calculation is not possible | Qualcomm Incorporated |
| 4.4.3.3 | Maintenance for Receiver characteristics [NR_newRAT-Core] | |
| R4-2003528 | Clarifications on transmitter power for FR2 Rx requirements | MediaTek Inc. |
| R4-2003659 | Draft CR to TS 38.101-2 Retrieve the Maximum input level for FR2 DL 64QAM(R15) | China Telecom |
| 4.4.4 | Maintenance for general requirements in 38.101-3 [NR_newRAT-Core] | |
| R4-2005001 | FR1+FR2 CA BCS0 is a default | Nokia, Nokia Shanghai Bell |
| 4.4.4.1 | [FR1] Maintenance for Transmitter characteristics within FR1 [NR_newRAT-Core] | |
| R4-2003870 | Removal of the Annex modifiedMPR-Behaviour from the NSA specification | Ericsson |
| R4-2004390 | Draft CR to TS 38.101-3 on configured output power relaxation due to EN-DC (Rel-15) | ZTE Corporation |
| 4.4.4.3 | [FR1] Maintenance for Receiver characteristics within FR1 [NR_newRAT-Core] | |
| R4-2004395 | Draft CR to TS 38.101-3 on REFSENS relaxation due to EN-DC (Rel-15) | ZTE Corporation |
| 4.5 | UE EMC [NR_newRAT-Core] | |
| R4-2003988 | DraftCR to TS 38.124: specification corrections and removal of [], Rel-15 | Huawei |
| R4-2003989 | DraftCR to TS 38.124: correction of UE radiated spurious emissons requirement, Rel-15 | Huawei |
| R4-2003990 | DraftCR to TS 38.124: correction of the Rx exclusion band, Rel-15 | Huawei |
| R4-2003991 | DraftCR to TS 38.124: Performance assessment, Rel-15 | Huawei |
| R4-2003992 | DraftCR to TS 38.124: Performance criteria, Rel-15 | Huawei |
| 4.6.1 | General [NR_newRAT-Core] | |
| R4-2004728 | Draft CR to 38.104 on Removal of brackets and TBD (Rel-15) | Ericsson |
| 4.6.2 | Transmitter characteristics maintenance [NR_newRAT-Core] | |
| R4-2003626 | Additional unwanted emission requirements for the EESS protection from band n257 and n258 | NTT DOCOMO, INC. |
| R4-2003767 | Draft CR to TS 38.104: Additional OTA unwanted emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2003768 | Draft CR to TS 38.141-2: Additional OTA unwanted emissions requirements for EESS protection | Nokia, Nokia Shanghai Bell |
| R4-2003769 | Draft CR to TS 38.104: Addition on n257 to cat B OTA spurious emissions | Nokia, Nokia Shanghai Bell |
| R4-2003770 | Draft CR to TS 38.141-2: Addition on n257 to cat B OTA spurious emissions | Nokia, Nokia Shanghai Bell |
| R4-2003967 | Draft CR to 38.104: Additional requirements for EESS protection | NEC |
| R4-2003968 | Draft CR to 38.141-2: Additional requirements for EESS protection | NEC |
| R4-2004085 | [BS RF]draftCR to TS 37.10 4on NR channel spacing catF | ZTE Corporation |
| R4-2004086 | [BS RF]draftCR to TS 37.141 on NR channel spacing catF | ZTE Corporation |
| R4-2004087 | [BS RF]draftCR to TS 38.104 on EESS protection of band n257 and n258 catF | ZTE Corporation |
| R4-2004088 | [BS RF]draftCR to TS 38.141-2 on EESS protection of band n257 and n258 catF | ZTE Corporation |
| R4-2004089 | [BS RF]on the EESS protection for 36--37GHz outcome of WRC-19 | ZTE Corporation |
| R4-2004730 | Draft CR to 38.104 on EESS protection for bands n257 and n258 (Rel-15) | Ericsson |
| R4-2004731 | Draft CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-15) | Ericsson |
| R4-2005026 | EESS protection from NR BS operation in 24.25 GHz to 27.5 GHz | Samsung |
| 4.6.3 | Receiver characteristics maintenance [NR_newRAT-Core] | |
| R4-2003755 | Draft CR to TS 38.104: Correction to out-of-band blocking requirements in subclause 7.5 and subclause 10.6 | Ericsson |
| 4.7.1 | General [NR_newRAT-Perf] | |
| R4-2003485 | Clarification on EVM equalizer calculation for NR BS conformance testing | Keysight Technologies UK Ltd, Rohde & Schwarz |
| R4-2003486 | Draft CR to 38.104: Annex B and C clarification on equlisation calculation (B.6, C.6) | Keysight Technologies UK Ltd, Rohde & Schwarz |
| R4-2003487 | Draft CR to 38.141-1: Annex H clarification on equlisation calculation (H.6) | Keysight Technologies UK Ltd, Rohde & Schwarz |
| R4-2003489 | Draft CR to 38.141-2: Annex J clarification on equlisation calculation (L.6) | Keysight Technologies UK Ltd, Rohde & Schwarz |
| 4.7.2.1 | eAAS specifications [NR_newRAT-Perf/Core] | |
| R4-2003763 | Draft CR to TS 37.145-2: Additional information about alignment needed for TRP measurements in Annex F.1 | Ericsson |
| R4-2003971 | TS 37.145-1: Corrections related to Foffset | Ericsson |
| R4-2003972 | TS 37.145-2: Corrections related to Foffset | Ericsson |
| R4-2004463 | CR to TS 37.145-2: Correcting the reference angular step equations (Annex F.2.2) | Nokia, Nokia Shanghai Bell |
| R4-2004465 | R to TS 37.145-2: Correcting the reference angular step equations (Annex F.2.2) | Nokia, Nokia Shanghai Bell |
| R4-2004943 | Draft CR to TS 37.145-2: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| 4.7.2.2 | MSR specifications [NR_newRAT-Perf/Core] | |
| R4-2003970 | TS 37.141: Corrections related to Foffset | Ericsson |
| R4-2004119 | TS 37.141 - Issues with TC applicabilities for CS17 and CS18 | Ericsson |
| R4-2004120 | Draft CR to TS 37.141 Rel-15 - Issues with TC applicabilities CS17 | Ericsson |
| R4-2004121 | Draft CR to TS 37.141 Rel-16 - Issues with TC applicabilities CS17-CS18 | Ericsson |
| 4.7.2.3 | NR conformance testing specifications [NR_newRAT-Perf] | |
| R4-2003766 | On updates related to tests in extreme conditions | Nokia, Nokia Shanghai Bell |
| R4-2003817 | Discussion on EVM and TPDR tests in NR conformance specifications | Nokia, Nokia Shanghai Bell |
| R4-2003818 | Draft CR to 38.141-1 with TPDR and EVM test model updates Rel-15 | Nokia, Nokia Shanghai Bell |
| R4-2003819 | Draft CR to 38.141-2 with TPDR and EVM test model updates Rel-15 | Nokia, Nokia Shanghai Bell |
| R4-2003973 | TS 38.141-1: Correction on testing under extreme conditions for BS output powerr | Ericsson |
| R4-2003974 | TS 38.141-2: Correction on testing under extreme conditions for BS radiated transmit power | Ericsson |
| R4-2003993 | DraftCR to TS 38.141-1: Corrections for the extreme environment testing , Rel-15 | Huawei |
| R4-2003994 | DraftCR to TS 38.141-2: Corrections for the extreme environment testing , Rel-15 | Huawei |
| R4-2004122 | Manufacturer declarations clarifications | Ericsson |
| R4-2004123 | Draft CR to TS 38.141-1 - Manufacturer declaration clarifications | Ericsson |
| R4-2004124 | Draft CR to TS 38.141-2 - Manufacturer declaration clarifications | Ericsson |
| R4-2004177 | DraftCR 38.141-1 4.9.2.3 corrections for random data generation | Futurewei Technologies |
| R4-2004178 | DraftCR 38.141-2 4.9.2.3 corrections for random data generation | Futurewei Technologies |
| R4-2004945 | Draft CR to TS 38.141-1: Clarifications and corrections on extreme test environment | Nokia, Nokia Shanghai Bell |
| R4-2004947 | Draft CR to TS 38.141-2: Clarifications of extreme test environment and corrections of references to annexes | Nokia, Nokia Shanghai Bell |
| 4.7.3 | Conducted conformance testing (38.141-1) [NR_newRAT-Perf] | |
| R4-2003760 | Draft CR to TS 38.141-1: Correction to out-of-band blocking requirement is subclause 7.5 | Ericsson |
| R4-2004944 | Draft CR to TS 38.141-1: Corrections on generation of test configurations | Nokia, Nokia Shanghai Bell |
| 4.7.4 | Radiated conformance testing (38.141-2) [NR_newRAT-Perf] | |
| R4-2003761 | Draft CR to TS 38.141-2: Correction to out-of-band blocking requirement in subclause 7.6 | Ericsson |
| R4-2004486 | Draft CR for TS 38.141-2: NR FR2 test models for 16QAM | Huawei, HiSilicon |
| R4-2004500 | CR to TS 38.141-2: Correcting the reference angular step equations (Annex I.2.2) | Nokia, Nokia Shanghai Bell |
| R4-2004504 | CR to TS 38.141-2: Correcting the reference angular step equations (Annex I.2.2) | Nokia, Nokia Shanghai Bell |
| R4-2004513 | CR to TS 38.141-2: Adding spherical angle definitions to 3.2 | Nokia, Nokia Shanghai Bell |
| R4-2004514 | CR to TS 38.141-2: Adding spherical angle definitions to 3.2 | Nokia, Nokia Shanghai Bell |
| R4-2004946 | Draft CR to TS 38.141-2: Correction on frequency offset symbols in test configurations | Nokia, Nokia Shanghai Bell |
| R4-2004948 | Draft CR to TS 38.141-2: Correction on test procedure of OTA in-channel selectivity | Nokia, Nokia Shanghai Bell |
| 4.8.1.1 | Emission requirements [NR_newRAT-Core] | |
| R4-2003995 | Clarifications to the direct field strength measurement of unwanted radiated emissions from the BS enclosure port | Huawei |
| R4-2003996 | DraftCR to TS 38.113: direct field strength measurements for the EMC RE, Rel-15 | Huawei |
| 4.8.1.2 | Immunity requirements [NR_newRAT-Core] | |
| R4-2004081 | [EMC]Discussion on using the reverberation chamber as a alternative test site for radiated immunity testing | ZTE Corporation |
| R4-2004082 | [EMC]draft CR to TS 37.113 Add the reverberation chamber for radiated immunity testing(clause 2&9.2.2 ) | ZTE Corporation |
| R4-2004083 | [EMC]draft CR to TS 37.114 Add the reverberation chamber for radiated immunity testing(clause 2&9.2.1) | ZTE Corporation |
| R4-2004084 | [EMC]draft CR to TS 38.113 Add the reverberation chamber for radiated immunity testing(clause 2&9.2.2 ) | ZTE Corporation |
| R4-2004558 | Proposal for use of reverberation chamber for receiver immunity testing | Ericsson |
| R4-2004559 | Draft CR to 37.113 Introducing Reverberation Chamber | Ericsson |
| R4-2004560 | Draft CR to 37.114 Introducing Reverberation Chamber | Ericsson |
| R4-2004561 | Draft CR to 37.113 Introducing Reverberation Chamber | Ericsson |
| R4-2004562 | On the need for EMC test reduction proposal | Ericsson |
| R4-2004563 | Proposal for EMC reduction of test configurations | Ericsson |
| R4-2004640 | Draft CR to 38.113 Introducing Reverberation Chamber | Ericsson Inc. |
| 4.9.1 | General [NR_newRAT-Core] | |
| R4-2004001 | On definition of TCI chain | ZTE Corporation |
| 4.9.2 | UE measurement capability (38.133/36.133) | |
| R4-2003599 | CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-freq. measurement (Section 9.2.3) | MediaTek inc. |
| R4-2004431 | Reporting Criteria discussion | Nokia, Nokia Shanghai Bell |
| R4-2004432 | LS on UE reporting criteria | Nokia, Nokia Shanghai Bell |
| R4-2004433 | Reporting Criteria in 36.133 | Nokia, Nokia Shanghai Bell |
| R4-2004434 | Draft CR to 36.133 for NR reporting criteria | Nokia, Nokia Shanghai Bell |
| R4-2004650 | Reporting criteria with NR | Ericsson |
| R4-2004651 | On reporting criteria with NR | Ericsson |
| R4-2004652 | On measurement reporting criteria with EN-DC | Ericsson |
| R4-2004653 | Response LS on measurement reporting criteria for EN-DC | Ericsson |
| R4-2004812 | Reporting criteria with NR | Ericsson-LG Co., LTD |
| 4.9.3 | RRM measurement and measurement gap (38.133/36.133) [NR_newRAT-Core] | |
| R4-2003088 | Requirements on measurements outside gaps for FR2 | Ericsson |
| R4-2003089 | Requirements on measurements outside gaps for FR2 | Ericsson |
| R4-2003598 | CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered (Section 9.2.5.1) | MediaTek inc. |
| R4-2004100 | Discussion on measurement reporting criteria for EN-DC | ZTE |
| R4-2004101 | Remaining issues on NR reporting criteria | ZTE |
| R4-2004102 | Reply LS on measurement reporting criteria for EN-DC | ZTE |
| R4-2004103 | draft CR to 36.133 on NR reporting criteria | ZTE |
| R4-2004286 | Correction on gap pattern applicability in TS 36.133 | Huawei, Hisilicon |
| R4-2004332 | Discussion on FR2 measurement outside gap | Huawei, HiSilicon, MediaTek |
| R4-2004333 | CR on FR2 measurement requriements outside gaps R15 | Huawei, HiSilicon, MediaTek |
| R4-2004334 | CR to remove RSTD requirements for NE-DC in 36.133 R15 | Huawei, HiSilicon |
| R4-2004335 | CR on inter-RAT RSTD requirements for NE-DC in 38.133 R15 | Huawei, HiSilicon |
| R4-2004430 | Discussion on SMTC configuration in FR2 | Nokia, Nokia Shanghai Bell |
| 4.9.5 | Connected state mobility (38.133/36.133) [NR_newRAT-Core] | |
| R4-2003395 | Correction of CFRA RSRP threshold | Nokia, Nokia Shanghai Bell |
| R4-2004281 | Discussion on RRC processing delay for RRC release with redirection | Huawei, Hisilicon |
| R4-2004833 | [CR] RRC release with redirection 38.133 R16 | ZTE Corporation |
| R4-2004834 | [CR] RRC release with redirection test cases 38.133 R15 | ZTE Corporation |
| R4-2004835 | [CR] RRC release with redirection 36.133 R15 | ZTE Corporation |
| R4-2004836 | [CR] RRC release with redirection 36.133 R16 Cat A | ZTE Corporation |
| R4-2004842 | Discussion on RRC procedure delay in RRC release with redirection | ZTE Corporation |
| R4-2004854 | Discussion on RRC re-establishment requirement | ZTE Corporation |
| R4-2004855 | CR on RRC re-establishment requirements R15 | ZTE Corporation |
| R4-2004856 | CR on RRC re-establishment requirements R16 (Cat A) | ZTE Corporation |
| 4.9.6 | Timing (38.133/36.133) [NR_newRAT-Core] | |
| R4-2004284 | CR on UE transmit timing | Huawei, Hisilicon |
| 4.9.7 | Signaling characteristics (38.133/36.133) | |
| R4-2003493 | draftCR on TCI state switch | MediaTek inc. |
| R4-2003494 | Discussion on remaining issues of TCI state switch | MediaTek inc. |
| R4-2003574 | Corrections to R15 MAC-CE based TCI state switching requirements | Qualcomm Incorporated |
| R4-2003575 | CR for correction to MAC-CE based TCI State switch timeline (Clause 8.10.3) | Qualcomm Incorporated |
| R4-2003610 | CR for SCell activation delay in FR2 | MediaTek inc. |
| R4-2004238 | Correction on Correction on Psharingfactor | Huawei, Hisilicon, MediaTek |
| R4-2004277 | CR on interruption due to Acitve BWP switch | Huawei, Hisilicon |
| R4-2004282 | CR on CSI-RS based BFD | Huawei, Hisilicon |
| R4-2004283 | CR on CSI-RS based CBD | Huawei, Hisilicon |
| R4-2004287 | Correction onTCI state switching | Huawei, Hisilicon |
| R4-2004336 | Discussion on SCell activation requirements | Huawei, HiSilicon |
| R4-2004337 | CR on SCell activation requirements R15 | Huawei, HiSilicon |
| R4-2004417 | Draft CR 38.133 (8.10.5) Corrections to RRC-based TCI state change | Ericsson |
| R4-2004418 | On Correction to SCell Activation Delay Requirements | Ericsson |
| R4-2004419 | Draft CR 38.133 (8.3.2) Corrections to SCell Activation Delay Requirements | Ericsson |
| 4.9.8 | Beam management based on SSB and/or CSI-RS (38.133) [NR_newRAT-Core] | |
| R4-2003407 | draft CR on SMTC2 configuration in SSB based CBD for R15 | Apple |
| R4-2003611 | Scheduling restriction due to SSB configured for aperiodic L1-RSRP reporting on FR2 | MediaTek inc. |
| R4-2003612 | CR on SMTC period for beam management requirements | MediaTek inc., Huawei, HiSilicon |
| R4-2003613 | CR for CSI-RS based L1-RSRP measurement period | MediaTek inc. |
| R4-2004809 | QCL chain depth restriction in Rel-15 RRM requirements | Qualcomm |
| 4.10.1 | General [NR_newRAT-Perf] | |
| R4-2003495 | draftCR on PDSCH RMC | MediaTek inc. |
| R4-2004239 | Correction to E-UTRAN Serving Cell Parameters | Huawei, Hisilicon |
| R4-2004285 | Accuracy of carrier aggregation in NR | Huawei, Hisilicon |
| 4.10.2 | RRM test cases [NR_newRAT-Perf] | |
| R4-2003112 | Correction of NR SA FR2 inter-freq measurement reporting | Ericsson |
| R4-2003218 | DRAFT CR to TS 38.133: Clarifications to AoA setup Annex A.5 (Rel-15) | Rohde & Schwarz |
| R4-2003219 | DRAFT CR to TS 38.133: Clarifications to AoA setup Annex A.7 (Rel-15) | Rohde & Schwarz |
| R4-2003614 | CR on RACH test cases with CSI-RS resouece R15 | MediaTek inc. |
| R4-2004240 | Correction to inter-frequency measurement TCs | Huawei, Hisilicon |
| R4-2004241 | Correction to interruption TCs | Huawei, Hisilicon |
| R4-2004242 | Correction to FR1 SA inter-RAT measurement TCs_r16 | Huawei, Hisilicon |
| R4-2004243 | Correction to interruption TCs_r16 | Huawei, Hisilicon |
| R4-2004276 | CR for RRC Connection Release with Redirection | Huawei, Hisilicon |
| R4-2004278 | CR on RRC Re-establishment test cases | Huawei, Hisilicon |
| R4-2004279 | CR on Timing advance test cases for EN-DC | Huawei, Hisilicon |
| R4-2004280 | CR on Timing test cases for NR SA | Huawei, Hisilicon |
| R4-2004338 | CR on random access test case R15 | Huawei, HiSilicon |
| R4-2004339 | CR on L1-RSRP delay tests for FR2 | Huawei, HiSilicon |
| R4-2004340 | CR to L1-RSRP accuracy TC for FR2 EN-DC R15 | Huawei, HiSilicon |
| R4-2004341 | CR to L1-RSRP accuracy TC for FR2 SA R15 | Huawei, HiSilicon |
| R4-2004858 | FR2 PRACH Test cases in 38.133 Annex A | ANRITSU LTD |
| R4-2004859 | Update of FR2 PRACH Test cases | ANRITSU LTD |
| R4-2004860 | FR2 RLM Test cases with 2 Angles of Arrival in 38.133 Annex A | ANRITSU LTD |
| R4-2004861 | Update of FR2 RLM Test cases with 2 Angles of Arrival | ANRITSU LTD |
| R4-2004862 | UE Beam assumption for RRM Test cases in 38.133 Annex A | ANRITSU LTD |
| R4-2004863 | Add UE Beam assumption for selected RRM Test cases | ANRITSU LTD |
| 4.11.1 | UE demodulation and CSI (38.101-4) [NR_newRAT-Perf] | |
| R4-2003180 | Discussion on physical channels mapping and power ratios | Intel Corporation |
| R4-2003699 | CR updates to NR CSI test | Huawei, HiSilicon |
| R4-2003722 | Discussion on DL channel mapping and power ratio for NR UE performance requirements | Huawei, HiSilicon |
| R4-2003753 | TS38.101-4 draft CR: on DL channel signal power ratio | Huawei, HiSilicon |
| R4-2003754 | DL channel EPRE ratio parameters | Huawei, HiSilicon |
| R4-2004063 | Update of DL physical channels | Rohde & Schwarz |
| R4-2004552 | Draft CR to TS 38.101-4: Clarification on beamforming (R15) | Intel Corporation |
| R4-2004798 | Views on Channel Mapping for Rel-15 Tests | Qualcomm Incorporated |
| R4-2004857 | Correlation configuration for 4Rx in CQI/ PMI reporting TCs | ANRITSU LTD |
| 4.11.2 | BS demodulation (38.104) | |
| R4-2003463 | Draft CR to 38.104: Adding missing clause on Radiated Performance requirements for multi-slot PUCCH (11.3.1) | Keysight Technologies UK Ltd |
| R4-2003465 | Draft CR to 38.141-1: Adding missing TT value for BS demod testing (C.3) | Keysight Technologies UK Ltd |
| R4-2003466 | Draft CR to 38.141-2: Correction on required SNR value for multi-slot PUCCH testing (8.3.6) (C.3) | Keysight Technologies UK Ltd |
| R4-2003467 | Necessary corrections on Rel-15 BS Demodulation | Keysight Technologies UK Ltd |
| R4-2003886 | draftCR for 38.104: Performance requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | Nokia, Nokia Shanghai Bell |
| R4-2003887 | draftCR for 38.141-2: Radiated test requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | Nokia, Nokia Shanghai Bell |
| R4-2003888 | draftCR for 38.104: Performance requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | Nokia, Nokia Shanghai Bell |
| R4-2003889 | draftCR for 38.141-2: Radiated test requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | Nokia, Nokia Shanghai Bell |
| 4.12 | Maintenance of the Positioning specs (36.171, 37.171 and 38.171) [NR_newRAT-Perf or TEI] | |
| R4-2003279 | Draft CR for TS36.171, Introduction of BDS B1C in A-GNSS | CATT |
| R4-2003280 | Draft CR for TS38.171, Introduction of BDS B1C in A-GNSS | CATT |
| 5 | Rel-16 Work Items for LTE | |
| R4-2004827 | CR for Band 53 NS_45 requirement, AMPR, and OOB blocking | Qualcomm Incorporated |
| R4-2004828 | CR for Band 53 NS_45 requirement, AMPR, and OOB blocking | Qualcomm Incorporated |
| 5.1.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_intra-Core/Perf] | |
| R4-2004567 | Revised WID Basket WI for LTE Intra-band CA Rel-16 | Ericsson |
| R4-2004575 | TR 36.716-01-01 v0.6.0 Rel-16 LTE Intra-band | Ericsson |
| R4-2004582 | draft CR introduction of Rel-16 LTE Intra-band combinations in 36.101 | Ericsson |
| 5.2.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_1BUL-Core/Perf] | |
| R4-2003832 | Revised WID: Rel16 LTE inter-band CA for 2 bands DL with 1 band UL | Qualcomm Incorporated |
| R4-2003833 | Introduction of Rel-16 LTE inter-band CA for 2 bands DL with 1 band UL combinations in TS36101 | Qualcomm Incorporated |
| R4-2003834 | TR 36.716-02-01-030 Rel-16 2 Bands DL and 1 Band UL CA | Qualcomm Incorporated |
| 5.2.2 | UE RF with harmonic, close proximity and isolation issues | |
| R4-2003939 | TP for TR 36.716-02-01: CA_20A-41A\CA_20A-41C\CA_20A-41D | Huawei, HiSilicon |
| 5.2.3 | UE RF without specific issues [LTE_CA_R16_2BDL_1BUL-Core] | |
| R4-2003113 | TP for TR 36.716-02-01: CA_1A-41C | Samsung, KDDI |
| R4-2003114 | TP for TR 36.716-02-01: CA_18-41 | Samsung, KDDI |
| R4-2003422 | TP for TR 36.716-02-01-070 for CA band combinations CA_46A-48B, CA_46B-48B, CA_46C-48B, CA_46D-48B and CA_46E-48B for single UL and dual UL | Charter Communications, Inc |
| 5.3.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_3BDL_1BUL-Core/Perf] | |
| R4-2004769 | Introduction of completed R16 3DL band combinations to TS 36.101 | Huawei, HiSilicon |
| R4-2004771 | Revised WID for LTE inter-band CA for 3 bands DL with 1 bands UL | Huawei, HiSilicon |
| 5.3.3 | UE RF without specific issues [LTE_CA_R16_3BDL_1BUL-Core] | |
| R4-2003115 | TP for TR 36.716-03-01: CA_1A-18A-41A and CA_1A-18A-41C | Samsung, KDDI |
| R4-2003791 | TP for TR 36.716-03-01: CA_1-20-38 | ZTE Corporation |
| 5.4.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_1BUL-Core] | |
| R4-2003389 | Revised WI: Rel'16 LTE inter-band CA for x bands DL (x=4, 5) with 1 band UL | Nokia, Nokia Shanghai Bell |
| R4-2003390 | TR 36.716-04-01 v0.9.0 | Nokia, Nokia Shanghai Bell |
| R4-2004505 | Introduction of LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL to TS36.101 | Nokia, Nokia Shanghai Bell |
| 5.5.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_2BUL-Core] | |
| R4-2004823 | Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL | Huawei, HiSilicon |
| R4-2004824 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 | Huawei, HiSilicon |
| 5.5.3 | UE RF without specific issues [LTE_CA_R16_2BDL_2BUL-Core] | |
| R4-2003116 | TP for TR 36.716-02-02: CA_1A-41C | Samsung, KDDI |
| R4-2003117 | TP for TR 36.716-02-02: CA_18-41 | Samsung, KDDI |
| 5.6.1 | Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_2BUL-Core] | |
| R4-2003220 | TR 36.716-03-02 v0.10.0 LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 | LG Electronics France |
| R4-2003221 | Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 | LG Electronics France |
| R4-2003222 | Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 | LG Electronics France |
| 5.6.2 | UE RF with MSD [LTE_CA_R16_xBDL_2BUL-Core] | |
| R4-2003242 | TP on summary of self-interference analysis for new x bands (x=3,4,5) DL with 2 bands UL | LG Electronics Polska |
| R4-2003244 | MSD results for LTE-A inter-band CA for x bands DL (x=3,4,5) with 2 bands UL in Rel-16 | LG Electronics Polska |
| 5.6.3 | UE RF without MSD | |
| R4-2003118 | TP for TR 36.716-03-02: CA_1A-18A-41A and CA_1A-18A-41C | Samsung, KDDI |
| R4-2003245 | TP on 3 bands DL and 2 bands UL CA in Rel-16 | LG Electronics Polska |
| R4-2003246 | TP on 4 bands DL and 2 bands UL CA in Rel-16 | LG Electronics Polska |
| 5.10.2 | Coexistence with NR [LTE_eMTC5] | |
| R4-2004077 | TP for TR 37.823: Power boosting for LTE-MTC | Nokia, Nokia Shanghai Bell |
| R4-2004162 | TR 37.823 LTE-M coexisting with NR v 0.5.0 | Ericsson |
| 5.10.3.1 | DL quality report in MSG3 and connected mode [LTE_eMTC5-Core] | |
| R4-2004014 | Discussion on the remaining issues on DL quality report for eMTC | Ericsson |
| R4-2004015 | Draft CR: Introduction of DL channel quality report for eMTC | Ericsson |
| R4-2004377 | CR on for quality reporting | Huawei, HiSilicon |
| 5.10.3.3 | MPDCCH performance improvement | |
| R4-2003564 | Simulation results for MPDCCH performance improvements of RLM tests in MTC | Qualcomm Incorporated |
| R4-2004016 | RLM for enhanced MPDCCH | Ericsson |
| R4-2004017 | Draft CR: Introduction of RLM requirements with enhanced MPDCCH | Ericsson |
| 5.10.3.4 | PUR [LTE_eMTC5-Core] | |
| R4-2004187 | Overview of the PUR agreements for Rel-16 MTC | Ericsson, Nokia, Nokia Shanghai Bell |
| R4-2004188 | Introduction of requirements for preconfigured uplink resource transmission for cat-M1 | Ericsson, Nokia, Nokia Shanghai Bell |
| R4-2004378 | Discussion on capturing RRM requirements for PUR in Rel-16 eMTC | Huawei, HiSilicon |
| R4-2004379 | CR on measurement requirements for RSRP change based TA validation | Huawei, HiSilicon |
| 5.10.3.5 | Mobility enhancement [LTE_eMTC5-Core] | |
| R4-2003565 | On RSS-based RSRP measurement in R16 eMTC | Qualcomm Incorporated |
| R4-2004185 | Discussions on RSS measurement support for Rel-16 MTC | Ericsson |
| R4-2004186 | Draft CR: RA using RSS based RSRP measurement for cat-M | Ericsson |
| R4-2004380 | Discussion on remaining issues in RSS measurement | Huawei, HiSilicon |
| R4-2004381 | CR on RSS based measurement accuracy requirements | Huawei, HiSilicon |
| 5.10.4 | Demodulation and CSI requirements (36.101/36.104) [LTE_eMTC5-Perf] | |
| R4-2003563 | Simulation results for MPDCCH performance improvements of demod tests in MTC | Qualcomm Incorporated |
| R4-2003695 | Discussion on open issues for additional MTC enhancements for LTE | Huawei, HiSilicon |
| R4-2003696 | Discussion on the requirements for MPDCCH | Huawei, HiSilicon |
| R4-2003697 | Discussion on the requirements for CSI-RS based CSI reporting | Huawei, HiSilicon |
| R4-2004018 | Simulation results of MPDCCH with DMRS+CRS | Ericsson |
| R4-2004019 | Simulation results of CSI-RS based PMI reporting test | Ericsson |
| R4-2004020 | Open issues on UE/BS demodulation requirements for Rel-16 eMTC | Ericsson |
| R4-2004073 | UE and BS demodulation requirements for LTE_eMTC5 | Nokia, Nokia Shanghai Bell |
| 5.11.1 | General [NB_IOTenh3] | |
| R4-2003987 | NBIOT guard band operation for FCC regulation considerations | MediaTek Inc. |
| 5.11.2 | Co-existence with NR [NB_IOTenh3] | |
| R4-2003592 | Draft TR 37.824 v050 Coexistence between NB-IoT and NR | Futurewei Technologies |
| R4-2004949 | Draft CR to TS 37.141: Correction on optional support of NB-IoT operation in NR in-band with CS17 | Nokia, Nokia Shanghai Bell |
| 5.11.3.2 | PUR [NB_IOTenh3-Core] | |
| R4-2004256 | CR on measurement requriements for RSRP change based TA validation | Huawei, Hisilicon |
| 5.11.3.3 | Multi-carrier operations [NB_IOTenh3-Core] | |
| R4-2003566 | Remaining issues on RRM measurements in non-anchor carrier for NB-IoT | Qualcomm Incorporated |
| R4-2004075 | On NRSRP processing in multicarrier operation | Nokia, Nokia Shanghai Bell |
| R4-2004195 | Remaining discussions on non-anchor carrier RRM measurements | Ericsson |
| R4-2004253 | CR on downlink channel quality measurement requirement for Rel-16 NB IoT | Huawei, Hisilicon |
| R4-2004254 | CR on non-anchor RRM measurement requirements in enhanced coverage for Rel-16 NB IoT | Huawei, Hisilicon |
| R4-2004255 | CR on non-anchor RRM measurement requirements in normal coverage for Rel-16 NB IoT | Huawei, Hisilicon |
| R4-2004257 | Discussion on the non-anchor RRM measurement requirements in Rel-16 NB IoT | Huawei, Hisilicon |
| 5.11.3.4 | Others | |
| R4-2004076 | On TA offset configuration for NB-IoT coexistence with NR | Nokia, Nokia Shanghai Bell |
| R4-2004193 | NTA offset under NR and NB-IoT coexistence in 38.133 | Ericsson, Nokia, Nokia Shanghai Bell |
| R4-2004194 | Analysis of NTA offset under NR and NB-IoT coexistence | Ericsson |
| R4-2004258 | Discussion on the TA offset setting for NR and NB-IoT coexistence | Huawei, Hisilicon |
| R4-2004259 | Discussion on UE specific DRX for R16 NB-IoT | Huawei, Hisilicon |
| 5.11.4 | Demodulation and CSI requirements (36.101/36.104) [NB_IOTenh3-Perf] | |
| R4-2003704 | Discussion on NPDSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2003705 | Discussion on NPUSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2003743 | Discussion on NPDSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2003744 | Discussion on NPUSCH performance requirements for additional enhancements for NB-IOT | Huawei, HiSilicon |
| R4-2004021 | Open issues on UE/BS demodulation requirements for Rel-16 NB-IoT | Ericsson |
| R4-2004074 | UE and BS demodulation requirements for NB_IOTenh3 | Nokia, Nokia Shanghai Bell |
| 5.12.1.1 | Conditional handover [LTE_feMob-Core] | |
| R4-2003576 | Corrections to handover delay requirements for conditional HO | Qualcomm Incorporated |
| R4-2004522 | CR on 36133 LTE CHO | Nokia, Nokia Shanghai Bell |
| 5.12.1.2 | Reduction of user data interruption [LTE_feMob-Core] | |
| R4-2003110 | Considerations for LTE DAPS handover | Ericsson |
| R4-2003111 | Correction to DAPS HO requirements in 36.133 | Ericsson |
| R4-2003577 | Corrections to LTE DAPS HO requirements | Qualcomm Incorporated |
| R4-2004306 | CR on DAPS handover | Huawei, Hisilicon |
| R4-2004523 | CR on 36133 LTE DAPS handover | Nokia, Nokia Shanghai Bell |
| 5.13.4 | BS Demodulation requirements (36.104) [LTE_high_speed_enh2-Perf] | |
| R4-2003632 | Draft CR to TS 36.104 Finalization on PUSCH performance requirements for enhanced HST scenario | NTT DOCOMO, INC. |
| R4-2003633 | Draft CR to TS 36.141 Finalization on PUSCH performance requirements for enhanced HST scenario | NTT DOCOMO, INC. |
| R4-2003634 | Draft CR to TS 36.104 Finalization on PRACH performance requirements for enhanced HST scenario | NTT DOCOMO, INC. |
| R4-2003635 | Draft CR to TS 36.141 Finalization on PRACH performance requirements for enhanced HST scenario | NTT DOCOMO, INC. |
| 5.14 | LTE-based 5G terrestrial broadcast | |
| R4-2004145 | Impacts on BS RF requirement of new introduced numerology | ZTE Corporation |
| R4-2004146 | Draft CR to 36.104: Introduction of LTE based 5G terrestrial broadcast numerologies | ZTE Corporation |
| R4-2004147 | Draft CR to 36.101: Introduction of LTE based 5G terrestrial broadcast numerologies | ZTE Corporation |
| 5.14.2 | Demodulation and CSI requirements (36.101) [LTE_terr_bcast -Perf] | |
| R4-2003425 | On LTE-based 5G terrestrial broadcast demod requirement | Qualcomm, Inc. |
| R4-2003426 | CR: Demod requirement for 5G broadcast | Qualcomm, Inc. |
| R4-2003706 | Simulation results on UE performance requirements for LTE-based 5G terrestrial broadcast | Huawei, HiSilicon |
| R4-2003745 | Discuss and simulation results on UE performance requirements for LTE-based 5G terrestrial broadcast | Huawei, HiSilicon |
| 5.16.2 | Demodulation requirements (36.101) [LTE_DL_MIMO_EE-Perf] | |
| R4-2003698 | Discussion on the performance requirements for DL MIMO efficiency enhancements for LTE | Huawei, HiSilicon |
| 6.1.1 | System Parameters [NR_unlic-Core] | |
| R4-2003211 | On guardband for 60 kHz SCS | Intel Corporation |
| R4-2004491 | Further considerations of spectrum utilization for NR-U | Huawei, HiSilicon |
| R4-2004492 | Further considerations on guard band on wideband operation | Huawei, HiSilicon |
| R4-2004685 | Further considerations on the in-carrier bands and wideband operation for NR-U | Apple Inc. |
| R4-2004810 | Discussion on 6 GHz NR-U band details | Nokia, Nokia Shanghai Bell |
| 6.1.2 | UE RF requirements [NR_unlic-Core] | |
| R4-2004588 | TP for TR 38.716-02-00 to include CA_n25A-n46A | Ericsson, T-Mobile, MediaTek |
| R4-2004589 | TP for TR 38.716-02-00 to include CA_n46A-n66A | Ericsson, T-Mobile, MediaTek |
| R4-2004590 | TP for TR 37.716-11-11 to include DC_2A_n46A | Ericsson, T-Mobile, MediaTek |
| R4-2004591 | TP for TR 37.716-11-11 to include DC_66A_n46A | Ericsson, T-Mobile, MediaTek |
| R4-2004727 | Introduction of NR-based access to unlicensed spectrum | Qualcomm Incorporated |
| 6.1.2.1 | Transmitter characteristics [NR_unlic-Core] | |
| R4-2003871 | Initial simulations of required MPR and A-MPR for PC5 and prerequisites for PC3 | Ericsson |
| R4-2004232 | NR-U - Capturing the Spectral Emission Mask | Nokia, Nokia Shanghai Bell |
| R4-2004233 | NR-U - draft CR to introduce SEM and ACLR for NR-U to TS 38.101-1 | Nokia, Nokia Shanghai Bell |
| R4-2004234 | NR-U - draft CR to introduce SEM and ACLR for NR-U to TS 38.104 | Nokia, Nokia Shanghai Bell |
| R4-2004235 | NR-U - Wideband operation and Intra-Carrier Guardbands | Nokia, Nokia Shanghai Bell |
| R4-2004236 | NR-U - draft CR to introduce guardband design for NR-U to TS 38.101-1 | Nokia, Nokia Shanghai Bell |
| R4-2004237 | NR-U - Power Classes and Network Signalling values for Band n46 | Nokia, Nokia Shanghai Bell |
| R4-2004490 | Considerations of in-band emissions for NR-U | Huawei, HiSilicon |
| R4-2004723 | NR-U Occupied bandwidth requirement | Qualcomm Incorporated |
| R4-2004724 | NR-U In-band emissions requirement | Qualcomm Incorporated |
| R4-2004725 | NR-U MPR for PC5 single carrier and wideband | Qualcomm Incorporated |
| R4-2004933 | [NRU] EVM Budget and Other Assumptions for MPR and Applying NRU Masks | Skyworks Solutions Inc. |
| R4-2004934 | [NRU] MPR and Partial A-MPR for QPSK Waveforms | Skyworks Solutions Inc. |
| R4-2004936 | [NRU] UE Power Class Definition and Options | Skyworks Solutions Inc. |
| 6.1.2.2 | Receiver characteristics [NR_unlic-Core] | |
| R4-2003529 | NR-U receiver ACS and blocking requirements for n46 | MediaTek Inc. |
| R4-2003872 | UE RF receiver characteristics for NR-U | Ericsson |
| R4-2004694 | ACS requirement for NR-U | Apple Inc. |
| R4-2004726 | NR-U receiver ACS and blocking | Qualcomm Incorporated |
| 6.1.3 | Band combination related (Analysis, TPs, etc.) [NR_unlic-Core] | |
| R4-2003413 | Standalone NR-U combinations in Rel-16 | Ericsson |
| R4-2003414 | Draft CR on Introduction of standalone NR-U combinations in Rel-16 | Ericsson |
| R4-2003415 | TP on Inclusion of NR-U standalone combinations in TR 38 716-01-01: | Ericsson |
| R4-2003420 | [DC] TP for TR 37.716-11-11 for DC_48-n46 | Charter Communications, Inc |
| R4-2003423 | TP for TR 38.716-02-00 for CA_n48-n46 | Charter Communications, Inc |
| R4-2003873 | Completion of new NR-U CA bandwidth classes and specification of nominal CA carrier spacing | Ericsson |
| 6.1.4 | BS RF requirements [NR_unlic-Core] | |
| R4-2003812 | Draft CR to TS 37.107 with introduction of NR-U feature – core part | Nokia, Nokia Shanghai Bell |
| R4-2003813 | Draft CR to TS 38.104: Introduction of NR-U in core specification | Nokia, Nokia Shanghai Bell |
| 6.1.4.1 | Transmitter characteristics [NR_unlic-Core] | |
| R4-2004811 | NR-U - draft CR to introduce SEM and ACLR for NR-U to TS 38.104 | Nokia, Nokia Shanghai Bell |
| 6.1.4.2 | Receiver characteristics [NR_unlic-Core] | |
| R4-2003702 | NR-U BS REFSENSICS | Huawei, HiSilicon |
| R4-2003703 | NR-U BS dynamic range | Huawei, HiSilicon |
| R4-2003742 | NR-U BS dynamic range | Huawei, HiSilicon |
| R4-2003814 | Updated summary of simulation results for NR-U BS Rx FRC | Nokia, Nokia Shanghai Bell |
| R4-2003815 | NR-U BS REFSENS and ICS requirements | Nokia, Nokia Shanghai Bell |
| R4-2003816 | NR-U BS Dynamic range requirement | Nokia, Nokia Shanghai Bell |
| R4-2004043 | NR-U BS RX Simulation Results | Ericsson |
| R4-2004044 | NR-U BS RF RX Requirements for 60 kHz SCS | Ericsson |
| R4-2004159 | simulation results for NR-U BS RX FRC | ZTE Corporation |
| R4-2004160 | NR-U BS RX REFSENS and dynamic range requirement | ZTE Corporation |
| R4-2004161 | NR-U BS RX ICS requirement | ZTE Corporation |
| R4-2004488 | NR-U BS REFSENS | Huawei, HiSilicon |
| R4-2004489 | NR-U BS dynamic range | Huawei, HiSilicon |
| 6.1.5.1 | General (specification structure, etc) [NR_unlic-Core] | |
| R4-2003093 | Requirements applicability for NR-U | Ericsson |
| R4-2003094 | Updates to General section for NR-U in 38.133 | Ericsson |
| R4-2003095 | Updates to General section for NR-U in 36.133 | Ericsson |
| R4-2004843 | CR for spec structure to address NR-U in 38.133 v3 | ZTE Corporation |
| R4-2004844 | Discussion on approaches to address NR-U in 38.133 v3 | ZTE Corporation |
| 6.1.5.2 | Cell re-selection [NR_unlic-Core] | |
| R4-2003551 | Remaining issues on cell reselection in NR-U | Qualcomm Incorporated |
| R4-2004182 | Remaining discussions on IDLE mode cell re-selection requirements for NR-U | Ericsson |
| R4-2004183 | Draft CR: NR-U requirements for IDLE/INACTIVE states | Ericsson |
| R4-2004184 | NR-U inter-RAT requirements for IDLE/INACTIVE states | Ericsson |
| R4-2004260 | CR on introduction of RRC_IDLE state moblity requirements for NR-U | Huawei, Hisilicon |
| R4-2004266 | CR on introduction of RRC_INACTIVE state moblity requirements for NR-U | Huawei, Hisilicon |
| R4-2004269 | Discussion on cell reselection for NR-U | Huawei, Hisilicon |
| 6.1.5.3 | Handover [NR_unlic-Core] | |
| R4-2003665 | Draft CR to TS 36.133: adding handover to NR-U | Nokia, Nokia Shanghai Bell |
| R4-2003666 | Draft CR to TS 38.133: adding NR-U Handover. | Nokia, Nokia Shanghai Bell |
| 6.1.5.4 | RRC connection mobility control | |
| R4-2003838 | UE behavior in RRC release with re-direction in NR-U | ZTE Corporation |
| 6.1.5.5 | SCell activation/deactivation (delay and interruption) [NR_unlic-Core] | |
| R4-2003552 | On Scell activation and deactivation requirements in NR-U | Qualcomm Incorporated |
| R4-2003553 | Introduction of activation and deactivation delay requirements for SCells operating with CCA | Qualcomm Incorporated |
| R4-2004273 | Discussion on scell activation for NR-U | Huawei, Hisilicon |
| R4-2004657 | On SCell activation delay in NR-U | Ericsson |
| 6.1.5.6 | PSCell addition/release (delay and interruption) [NR_unlic-Core] | |
| R4-2003554 | On PSCell addition and release requirements in NR-U | Qualcomm Incorporated |
| R4-2003555 | Introduction of addition and release of NR PSCell operating with CCA in EN-DC | Qualcomm Incorporated |
| 6.1.5.7 | Active TCI state switching [NR_unlic-Core] | |
| R4-2003556 | On active TCI switching requirements in NR-U | Qualcomm Incorporated |
| R4-2003615 | Discussion on TCI switch requirement for NR-U | MediaTek inc. |
| R4-2004264 | CR on introduction of Active TCI state switching delay with CCA Requirements for NR-U | Huawei, Hisilicon |
| R4-2004658 | On active TCI state switching requirements in NR-U | Ericsson |
| 6.1.5.8 | Interruptions due to operation in non-NR-U serving cells [NR_unlic-Core] | |
| R4-2004261 | CR on interruption due to Active BWP switching on consistent LBT failure for NR-U | Huawei, Hisilicon |
| 6.1.5.9 | Active BWP switching [NR_unlic-Core] | |
| R4-2003557 | On new UL BWP switching requirements in NR-U | Qualcomm Incorporated |
| R4-2004263 | CR on introduction of Active BWP switching delay requirements for NR-U | Huawei, Hisilicon |
| R4-2004268 | Discussion on BWP switch for NR-U | Huawei, Hisilicon |
| R4-2004402 | Analysis of BWP switching requirement due to consistent UL failure | Ericsson |
| R4-2004403 | BWP switching delay requirement due to consistent UL failure in 38.133 | Ericsson |
| R4-2004404 | BWP switching interruption requirement due to consistent UL failure in 38.133 | Ericsson |
| R4-2004405 | Interruption due to BWP switching at consistent UL failure in 36.133 | Ericsson |
| R4-2004938 | On BWP switch in NR-U | ZTE Corporation |
| 6.1.5.10 | RLM and link recovery procedures [NR_unlic-Core] | |
| R4-2003558 | On RLM requirements in NR-U | Qualcomm Incorporated |
| R4-2003616 | Discussion on RLM requirement for NR-U | MediaTek inc. |
| R4-2003669 | Discussion on RLM requirements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2003975 | On RLM for NR-U | OPPO |
| R4-2004032 | Beam management in NR-U | Ericsson |
| R4-2004033 | Draft CR: Introduction of link recovery requirements with CCA | Ericsson |
| R4-2004272 | Discussion on RLM and link recovery for NR-U | Huawei, Hisilicon |
| R4-2004659 | On RLM in NR-U | Ericsson |
| R4-2004660 | Introduction of RLM requirements for NR-U | Ericsson |
| R4-2004939 | Discussion on RLM in NR-U | ZTE Corporation |
| 6.1.5.11 | Measurement requirements | |
| R4-2003398 | Remaining issues on cell detection and serving cell measurement for NR-U | Apple |
| R4-2003559 | Remaining issues on measurement requirements in NR-U | Qualcomm Incorporated |
| R4-2003560 | On RSSI and CO measurements in NR-U | Qualcomm Incorporated |
| R4-2003617 | Discussion on measurement on QCL-ed SSBs and measurement capability for NR-U | MediaTek inc. |
| R4-2003618 | Discussion on SFTD measurements towards NR-U with LBT | MediaTek inc. |
| R4-2003619 | Discussion on RSSI measurement for NR-U | MediaTek inc. |
| R4-2003667 | Draft CR to TS 38.133: adding NR-U inter-frequency measurements | Nokia, Nokia Shanghai Bell |
| R4-2003668 | Draft CR to TS 36.133: adding inter-RAT NR-U measurements | Nokia, Nokia Shanghai Bell |
| R4-2003670 | RSSI and Channel Occupancy Measurements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2003671 | SSB measurements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2003672 | On the impact of UL LBT failure in measurement reporting | Nokia, Nokia Shanghai Bell |
| R4-2003673 | Discussion on L1-RSRP measurements in NR-U | Nokia, Nokia Shanghai Bell |
| R4-2003839 | PBCH payload reading for SSB index identification in NR-U | ZTE Corporation |
| R4-2004034 | L1-RSRP measurements in NR-U | Ericsson |
| R4-2004035 | Draft CR: Introduction of L1-RSRP measurement requirements with CCA | Ericsson |
| R4-2004262 | CR on introduction of intra-frequency measurements requirements for NR-U | Huawei, Hisilicon |
| R4-2004270 | Discussion on L1-RSRP measurement requirement for NR-U | Huawei, Hisilicon |
| R4-2004271 | Discussion on measurement requirement for NR-U | Huawei, Hisilicon |
| R4-2004274 | Discussion RSSI measurement for NR-U | Huawei, Hisilicon |
| R4-2004426 | On Inter-RAT SFTD for NR-U | Ericsson |
| R4-2004656 | On RSSI and channel occupancy measurement requirements | Ericsson |
| R4-2004661 | On the impact of UL LBT failures on measurement reporting delay | Ericsson |
| R4-2004662 | On intra-frequency measurements in NR-U | Ericsson |
| R4-2004663 | On inter-frequency measurements in NR-U | Ericsson |
| R4-2004845 | CR to address NR-U in EN-DC SFTD measurements in 36.133 | ZTE Corporation |
| R4-2004846 | Discussion on inter-RAT SFTD measurement towards NR-U | ZTE Corporation |
| R4-2004847 | CR to address NR-U in inter-RAT SFTD measurements in 36.133 | ZTE Corporation |
| R4-2004940 | L1-RSRP measurement in NR-U | ZTE Corporation |
| R4-2004941 | UE behaviour under successive UL LBT failures during event-triggered reporting | ZTE Corporation |
| R4-2004942 | Pending issues on cell detection and serving cell measurement under NR-U | ZTE Corporation |
| 6.1.5.12 | Measurement capability and reporting criteria [NR_unlic-Core] | |
| R4-2003561 | On measurement capabilities and reporting criteria in NR-U | Qualcomm Incorporated |
| R4-2004265 | CR on introduction of reporting criteria for NR-U | Huawei, Hisilicon |
| R4-2004267 | Discussion measurement capability for NR-U | Huawei, Hisilicon |
| R4-2004275 | [Draft] LS on transmit power of CSI-RS across different occasions | Huawei, Hisilicon |
| R4-2004664 | On measurement reporting criteria for NR-U | Ericsson |
| R4-2004850 | RSSI measurement and report mapping for NR-U | ZTE Corporation |
| 6.1.5.13 | Timing | |
| R4-2003411 | Draft CR on UE transmit timing accuracy and timing reference cell under DL LBT failure | Ericsson |
| R4-2003412 | On the timing reference cell adaptation under DL LBT failure in reference cell | Ericsson |
| R4-2003620 | CR for timing requirement for NR-U | MediaTek inc. |
| R4-2004848 | on timing reference cell adjustment for NR-U | ZTE Corporation |
| R4-2004849 | [LS] timing reference cell adjustment under NR-U | ZTE Corporation |
| 6.2.1 | General [NR_CLI_RIM-Core] | |
| R4-2003233 | Reply LS on CLI measurement and reporting | LG Electronics Inc. |
| 6.2.2 | RRM core requirements maintenance (38.133) [NR_CLI_RIM-Core] | |
| R4-2003804 | 38.133 CR on CLI measurement requirements | Nokia, Nokia Shanghai Bell |
| R4-2004342 | Discussion on remaining issues in CLI measurement requirements | Huawei, HiSilicon |
| R4-2004343 | [draft] reply LS on CLI measurement and reporting | Huawei, HiSilicon |
| R4-2004344 | CR on CLI measurement requirements | Huawei, HiSilicon |
| 6.2.3 | RRM perf. requirements (38.133) [NR_CLI_RIM-Perf] | |
| R4-2003419 | Remaining issues of CLI RRM Performance Requirements | Qualcomm CDMA Technologies |
| 6.2.3.1 | CLI measurement accuracy [NR_CLI_RIM-Perf] | |
| R4-2003179 | SRS-RSRP measurement accuracy for FR2 | LG Electronics Inc. |
| R4-2003805 | Performance aspects for CLI measurement | Nokia, Nokia Shanghai Bell |
| R4-2004345 | Discussion on remaining issues in CLI performance requirements | Huawei, HiSilicon |
| R4-2004346 | CR on CLI measurement performance requirements | Huawei, HiSilicon |
| 6.2.3.2 | Test cases [NR_CLI_RIM-Perf] | |
| R4-2003223 | Discussion on CLI performance test cases | LG Electronics Inc. |
| R4-2003229 | Draft CR for event triggerred reporting tests for CLI | LG Electronics Inc. |
| R4-2003806 | Discussion on test cases in EN-DC | Nokia, Nokia Shanghai Bell |
| R4-2004347 | CR on test cases for SRS-RSRP measurement accuracy in FR1 | Huawei, HiSilicon |
| R4-2004348 | CR on test cases for SRS-RSRP measurement accuracy in FR2 | Huawei, HiSilicon |
| R4-2004349 | CR on test cases for CLI-RSSI measurement accuracy in FR1 | Huawei, HiSilicon |
| R4-2004350 | CR on test cases for CLI-RSSI measurement accuracy in FR2 | Huawei, HiSilicon |
| 6.3.2.1 | Handover with simultaneous Rx/Tx with source and target cells [NR_Mob_enh-Core] | |
| R4-2003090 | Considerations for NR DAPS handover | Ericsson |
| R4-2003091 | Correction to DAPS HO requirements in 38.133 | Ericsson |
| R4-2003193 | Discussion on remaining issues on DAPS handover | Intel Corporation |
| R4-2003194 | Draft CR to TS 38.133: DAPS handover RRM requirement | Intel Corporation |
| R4-2003562 | Remaining issues on NR DAPS HO | Qualcomm Incorporated |
| R4-2003605 | Discussion on dual active protocol stack handover | MediaTek inc. |
| R4-2003959 | Discussion on remaining open issues on DAPS handover | NEC |
| R4-2004308 | Further discussion on remaining issues on DAPS handover | Huawei, HiSilicon |
| R4-2004309 | DraftCR on DAPS handover requirements | Huawei, HiSilicon |
| R4-2004310 | Discussion on UE capabilities signalling on DAPS handover | Huawei, HiSilicon |
| R4-2004311 | Draft LS on UE capabilities on DAPS HO | Huawei, HiSilicon |
| R4-2004438 | CR correcting DAPS handover requirements | Nokia, Nokia Shanghai Bell |
| 6.3.2.2 | Conditional handover [NR_Mob_enh-Core] | |
| R4-2003195 | Draft CR to TS 38.133: CHO RRM requirement | Intel Corporation |
| R4-2004312 | DraftCR on conditional handover requirements | Huawei, HiSilicon |
| R4-2004435 | CR Introduction of handover delay requirements for conditional handover (section 6.1) | Nokia, Nokia Shanghai Bell |
| R4-2004436 | CR Introduction of handover delay requirements for conditional handover (section 6.1) | Nokia, Nokia Shanghai Bell |
| 6.3.2.3 | Conditional PSCell addition/change [NR_Mob_enh-Core] | |
| R4-2003196 | Draft CR to TS 38.133: CPC RRM requirement | Intel Corporation |
| R4-2004313 | DraftCR on conditional PSCell change requirements | Huawei, HiSilicon |
| R4-2004437 | Correction CR for Conditional PSCell Change | Nokia, Nokia Shanghai Bell |
| 6.3.2.4 | Others [NR_Mob_enh-Core] | |
| R4-2003092 | Testcases for LTE and NR mobility enhancements | Ericsson |
| 6.4.1 | General [5G_V2X_NRSL] | |
| R4-2003234 | TR update TR38.886 v0.6.0 | LG Electronics France |
| R4-2003674 | Considerations on improving the draft TR and TS for NR V2X | vivo |
| R4-2004744 | On synchronization scenario for NR V2X in licensed band | Huawei, HiSilicon |
| R4-2004746 | On scenarios of con-current operation | Huawei, HiSilicon |
| 6.4.2 | Co-existence Study [5G_V2X_NRSL-Core] | |
| R4-2003549 | TP on Indevice Coexistence | Futurewei Technologies |
| 6.4.3 | System parameters [5G_V2X_NRSL-Core] | |
| R4-2003281 | Discussion on Uu and SL combination for NR V2X | CATT |
| R4-2003282 | Draft Reply LS on Sidelink UE capability for (NG)EN-DC and NE-DC | CATT |
| R4-2003301 | On the introduction of frequency band and channel arrangement for NR V2X in TS 38.104 | CATT |
| R4-2003302 | Draft CR for TS38.104, Introduce frequency band and channel arrangement for NR V2X | CATT |
| R4-2003675 | Further discussion on channel bandwidth for NR V2X licensed bands | vivo |
| R4-2003676 | Discussion on sync mechanism between SL and Uu in NR V2X licensed bands | vivo |
| R4-2003677 | TP on channel bandwidths for NR V2X licensed band n38 | vivo |
| R4-2004972 | NR V2X licensed frequency bands for SL operation | CMCC |
| 6.4.4 | UE RF requirements [5G_V2X_NRSL-Core] | |
| R4-2003235 | TP on remaining issues for NR V2X UE | LG Electronics France |
| R4-2003237 | CR on NR V2X UE RF requirements for single carrier in TS38.101-1 | LG Electronics France |
| R4-2003240 | CR on NR V2X UE RF requirements for con-current operation or TDM operation in TS38.101-3 | LG Electronics France |
| R4-2003383 | Views on some remaining details for NR V2X SL/Uu concurrent operation | VODAFONE Group Plc |
| R4-2003840 | Updated CR on introducing RF requirements for 5G V2X service in TS38.101-1 in rel-16 | LG Electronics France |
| R4-2003847 | Draft CR on revised switching time and REFSENS requirements for EN-V2X UE in TS38.101-3 | LG Electronics France |
| R4-2003902 | CR on introducing EN-V2X UE and TDM operation between LTE SL and NR SL operation in TS38.101-3 | LG Electronics France |
| R4-2004747 | Draft CR for TS 38.101-3 Introduction of NR V2X cross RAT requirements | Huawei, HiSilicon |
| R4-2004748 | Draft CR for TS 38.101-1 Con-current operation for NR-V2X | Huawei, HiSilicon |
| 6.4.4.1 | Transmitter characteristics [5G_V2X_NRSL-Core] | |
| R4-2003239 | TP on NR V2X A-MPR (NS_33) and updated simulation results | LG Electronics Inc. |
| R4-2003283 | Discussion on time mask for NR V2X | CATT |
| R4-2003432 | CR for V2X sidelink transmission MPR | Qualcomm Incorporated |
| R4-2003433 | MPR for NR V2X PSSCH PSCCH transmission all channel bandwidths TP | Qualcomm Incorporated |
| R4-2003434 | MPR for PSFCH transmission all channel bandwidths TP | Qualcomm Incorporated |
| R4-2003435 | CR for A-MPR for V2X sidelink transmissions in n47 | Qualcomm Incorporated |
| R4-2003436 | A-MPR for 40MHz V2X PSSCH PSCCH transmission TP | Qualcomm Incorporated |
| R4-2003437 | A-MPR for 40MHz V2X PSFCH transmission TP | Qualcomm Incorporated |
| R4-2003438 | A-MPR for 10MHz V2X PSSCH PSCCH transmission TP | Qualcomm Incorporated |
| R4-2003439 | A-MPR for 10MHz V2X PSFCH transmission TP | Qualcomm Incorporated |
| R4-2003550 | On Simultaneous Transmission of PSFCH | Futurewei Technologies |
| R4-2003578 | On UL-SL Prioritization | Futurewei Technologies |
| R4-2003591 | Reply LS to RAN2 on UL-SL Prioritization | Futurewei Technologies |
| R4-2003881 | NR V2X specification structure for interband concurrent requirements Clause suffix and specification variants in 38.101-1 | Qualcomm Incorporated |
| R4-2004198 | MPR simulation results and discussion for PC3 PSSCH\PSCCH NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004199 | AMPR simulation results and discussion for PC3 PSSCH\PSCCH NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004200 | MPR\AMPR simulation results and discussion for PC2 PSSCH\PSCCH NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004201 | MPR\AMPR simulation results and discussion for PC3 PSFCH NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004202 | MPR\AMPR simulation results and discussion for PC2 PSFCH NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004203 | MPR\AMPR simulation results and discussion for PC3 S-SSB NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004204 | MPR\AMPR simulation results and discussion for PC2 S-SSB NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004205 | TP fo rTR38.886 to update MPR\AMPR requirements for both PC3 and PC2 NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004206 | DraftCR for 38.101-1 to specify MPR\AMPR requirements for PC3 NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004207 | DraftCR for 38.101-1 to specify configured transmitted power for NR V2X in band n47 | Huawei, HiSilicon |
| R4-2004415 | MPR simulations results for multi-UE PSFCH transmission | LG Electronics Finland |
| R4-2004468 | TX diversity for NR-V2X | Qualcomm Incorporated |
| R4-2004469 | Switching time between NR SL and LTE SL | Qualcomm Incorporated |
| R4-2004470 | ON_OFF V2X switching time mask | Qualcomm Incorporated |
| R4-2004471 | MPR A-MPR results for PSSS/SSSS/PSBCH transmission | Qualcomm Incorporated |
| R4-2004472 | REFSENS for NR V2X | Qualcomm Incorporated |
| R4-2004743 | On switching period for LTE SL and NR SL | Huawei, HiSilicon |
| R4-2004745 | On simultaneous transmission of PSFCH | Huawei, HiSilicon |
| 6.4.4.2 | Receiver characteristics [5G_V2X_NRSL-Core] | |
| R4-2003238 | TP on NR V2X UE REFSENS requirements at n47 | LG Electronics Inc. |
| R4-2003300 | Discussion on remaining issues on Rx RF requirements for NR V2X | CATT |
| R4-2003303 | Draft CR for TS38.101-1, Introduce Rx requirements for NR V2X single carrier | CATT |
| R4-2003304 | Draft CR for TS38.101-3, Introduce Rx requirements for NR V2X concurrent operation | CATT |
| 6.4.5 | RRM core requirements (38.133) [5G_V2X_NRSL-Core] | |
| R4-2003255 | Discussion the remaining issues for NR V2X RRM | CATT |
| R4-2004982 | Discussion of remaining issues for NR V2X | LG Electronics Inc. |
| 6.4.5.2 | Synchronization requirements [5G_V2X_NRSL-Core] | |
| R4-2003496 | Discussion on NR V2X synchronization requirement | MediaTek inc. |
| R4-2004314 | Simulation assumptions of PSBCH-RSRP measurement evaluation for NR V2X | Huawei, HiSilicon |
| R4-2004315 | DraftCR on PSBCH-RSRP accuracy requirements for NR V2X | Huawei, HiSilicon |
| 6.4.5.3 | Measurement requirements [5G_V2X_NRSL-Core] | |
| R4-2003427 | On NR V2X RSRP Measurement Side Conditions | Qualcomm, Inc. |
| R4-2003428 | On NR V2X Resource Selection Measurement Requirement | Qualcomm, Inc. |
| R4-2003497 | Discussion on NR V2X measurement requirement | MediaTek inc. |
| R4-2003498 | draftCR on L1 SL-RSRP measurements | MediaTek inc. |
| R4-2003499 | Link-level simulation results for NR V2X L1 SL-RSRP measurements | MediaTek inc. |
| R4-2004316 | Discussion on measurement related requirements for NR V2X | Huawei, HiSilicon |
| R4-2004317 | Simulation results of PSSCH-RSRP and PSCCH-RSRP measurements for NR V2X | Huawei, HiSilicon |
| R4-2004318 | DraftCR on L1 SL-RSRP accuracy requirements for NR V2X | Huawei, HiSilicon |
| R4-2004319 | DraftCR on SL-RSSI accuracy requirements for NR V2X | Huawei, HiSilicon |
| R4-2004983 | Measurement accuracy based on simulation results of PSSCH-RSRP and PSCCH-RSRP | LG Electronics Inc. |
| R4-2004984 | draft CR of NR V2X measurement accuracy requirements | LG Electronics Inc. |
| 6.4.5.4 | Interruption requirements [5G_V2X_NRSL-Core] | |
| R4-2003256 | Draft CR on interruption requirements for NR V2X | CATT |
| R4-2003429 | On NR V2X Interruption Requirement | Qualcomm, Inc. |
| R4-2003500 | Discussion on NR V2X interruption requirement | MediaTek inc. |
| R4-2004320 | Discussion on interruption related issues for NR V2X | Huawei, HiSilicon |
| R4-2004988 | draft CR of interruption for switching between NR SL and LTE SL | LG Electronics Inc. |
| 6.4.5.6 | Others [5G_V2X_NRSL-Core] | |
| R4-2004985 | draft CR of NR V2X operating band group | LG Electronics Inc. |
| R4-2004986 | draft CR of Annex.B for NR V2X side conditions | LG Electronics Inc. |
| R4-2004987 | draft CR of NR V2X abbreviations | LG Electronics Inc. |
| 6.5.1 | General [NR_IAB-Core] | |
| R4-2004801 | Email disccusion for updating IAB TS spec to capture RAN4 94b agreements | Qualcomm |
| R4-2004802 | Updated IAB TS spec based on RAN4 94 agreements | Qualcomm |
| R4-2005027 | Update on section 4 and section 5 based on latest agreement | Samsung |
| 6.5.1.1 | System parameters [NR_IAB-Core] | |
| R4-2003310 | Discussion of the open issues in IAB system parameters part | CATT |
| R4-2004172 | TP for TS 38.174 - system parameter | Ericsson |
| 6.5.1.2 | IAB-MT class [NR_IAB-Core] | |
| R4-2003313 | Discussion of IAB-MT class and Tx power | CATT |
| R4-2003774 | IAB-Node classification and related output power requirements | Nokia, Nokia Shanghai Bell |
| R4-2004148 | Discussion on IAB MT class | ZTE Corporation |
| R4-2004150 | Further discussion on IAB-MT power requirement | ZTE Corporation |
| R4-2004166 | IAB class definition | Ericsson |
| R4-2004545 | IAB class definitions | Huawei |
| R4-2004546 | TP to TS38.174 IAB class definitions | Huawei |
| R4-2004646 | On IAB-MT classes | Qualcomm Incorporated |
| R4-2004968 | Discussion on IAB class | CMCC |
| 6.5.1.3 | IAB-MT feature list [NR_IAB-Core] | |
| R4-2003315 | Discussion of IAB-MT feature list | CATT |
| R4-2003316 | LS on RAN4 IAB-MT feature list agreement | CATT |
| R4-2003608 | IAB-MT Feature List | Qualcomm Incorporated |
| R4-2004149 | Discussion on IAB MT feature list | ZTE Corporation |
| R4-2004169 | IAB-MT madatory feature | Ericsson |
| R4-2004487 | Discussion on R16 IAB MT RF features | Huawei, HiSilicon |
| R4-2005028 | Discussion on IAB-MT feature list | Samsung |
| 6.5.1.4 | Others [NR_IAB-Core] | |
| R4-2003846 | Multi-carrier and CA for IAB | Ericsson |
| 6.5.2 | RF requirements [NR_IAB-Core] | |
| R4-2003758 | TP to TR 38.xyz: Addition of antenna model and parameters in subclause 6.2 | Ericsson |
| R4-2004542 | TP to TS 38.174 -TX dynamic range | Huawei |
| R4-2004543 | TP to TS 38.174 -RX sensitivity | Huawei |
| R4-2004544 | TP to TS 38.174 -Rx dynamic range | Huawei |
| 6.5.2.1 | Conductive RF core requirements | |
| R4-2004096 | [IAB RF]on IAB TX IMD | ZTE Corporation |
| 6.5.2.1.1 | Transmitter characteristics [NR_IAB-Core] | |
| R4-2003311 | Discussion of IAB-MT frequency error requirement | CATT |
| R4-2003312 | Discussion of IAB-MT on/off time mask | CATT |
| R4-2004151 | frequency error requirement for IAB | ZTE Corporation |
| R4-2004152 | Further discussion on FR1 IAB-MT ACLR and ACS requirement | ZTE Corporation |
| 6.5.2.1.2 | Receiver characteristics [NR_IAB-Core] | |
| R4-2003314 | Discussion of IAB-MT reference sensitivity | CATT |
| R4-2004157 | In-band blocking for IAB MT | ZTE Corporation |
| 6.5.2.1.3 | TP to TS/TR [NR_IAB-Core] | |
| R4-2004097 | [IAB RF]TP to TS 38.174 IAB TX IMD | ZTE Corporation |
| R4-2004098 | [IAB RF] TP to TR 38.XXX IAB TX IMD | ZTE Corporation |
| R4-2004153 | TP to TR : IAB RX IM requirement (section 8.7 and 10.8) | ZTE Corporation |
| R4-2004154 | TP to TS 38.174: IAB RX IM requirement (section 7.7 and 10.8) | ZTE Corporation |
| R4-2004155 | TP to TR: IAB ICS requirement (section 8.8 and 10.9) | ZTE Corporation |
| R4-2004156 | TP to TS 38.174: IAB ICS requirement (section 7.8 and 10.9) | ZTE Corporation |
| R4-2004173 | TP for TS 38.174 - conducted RX spurious | Ericsson |
| R4-2004174 | TP for TR 38.xxx - conducted RX spurious | Ericsson |
| 6.5.2.2 | Radiated RF core requirements [NR_IAB-Core] | |
| R4-2004547 | IAB-MT ACLR and ACS | Huawei |
| R4-2004548 | Spurious emissions and regulator definitions. | Huawei |
| 6.5.2.2.1 | Transmitter characteristics [NR_IAB-Core] | |
| R4-2003609 | IAB-MT Tx Requirements | Qualcomm Incorporated |
| R4-2003775 | IAB-MT ACLR and ACS in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2004158 | Further discussion on FR2 IAB-MT ACLR and ACS requirement | ZTE Corporation |
| R4-2004163 | IAB MT unwanted emission for FR1 | Ericsson |
| R4-2004164 | IAB MT unwanted emission for FR2 | Ericsson |
| R4-2004165 | IAB MT TX dynamic range | Ericsson |
| R4-2004167 | IAB MT Frequency error | Ericsson |
| R4-2004168 | IAB MT power control requirement | Ericsson |
| R4-2004549 | IAB-MT FR1 Rx sensitivity requirement. | Huawei |
| R4-2004644 | Definition of IAB-MT ACLR requirement in FR2 | Qualcomm Incorporated |
| R4-2004647 | Definition of IAB-MT dynamic range | Qualcomm Incorporated |
| R4-2005029 | IAB-MT transmitter RF requirement | Samsung |
| 6.5.2.2.2 | Receiver characteristics [NR_IAB-Core] | |
| R4-2003757 | Further considerations regarding radiated IAB-Node reference sensitivity requirement | Ericsson |
| R4-2003776 | IAB-MT blocking requirements in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2003777 | IAB-MT receiver sensitivity declaration range in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2004170 | IAB MT inband blocking and ACS for FR1 | Ericsson |
| R4-2004171 | IAB MT inband blocking and ACS for FR2 | Ericsson |
| R4-2004550 | IAB-MT ACS wanted signal level. | Huawei |
| R4-2004551 | IAB-MT in band blocking | Huawei |
| R4-2004645 | Definition of IAB-MT in-band selectivity requirements in FR2 | Qualcomm Incorporated |
| R4-2005030 | IAB-MT receiver RF requirement | Samsung |
| 6.5.2.2.3 | TP to TS/TR [NR_IAB-Core] | |
| R4-2003759 | TP to TS 38.174: Addition of OTA IAB-Node out-of-band receiver blocking requirement in subclause 10.6 | Ericsson |
| R4-2004175 | TP for TS 38.174 - radiated RX spurious | Ericsson |
| R4-2004176 | TP for TR 38.xxx - radiated RX spurious | Ericsson |
| 6.5.3 | RRM core requirements (38.133) [NR_IAB-Core] | |
| R4-2004777 | on reference power corresponding to maxUplinkdutyCycle | Huawei, HiSilicon |
| 6.5.3.1 | General | |
| R4-2003531 | TP to IAB TR 38.8xx: The skeleton of IAB RRM requirement | Samsung |
| R4-2004247 | Discussion on R16 IAB features | Huawei, Hisilicon |
| 6.5.3.2 | RRC connection mobility control | |
| R4-2004246 | Discussion on RRC connection mobility control requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004252 | TP to TS 38.174 on random access requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004408 | Analysis of RRC re-establishment and RRC release requirements for IAB MT | Ericsson |
| R4-2004409 | TP to TS 38.174 v0.0.1: RRC re-establishment requirements for IAB MT | Ericsson |
| R4-2004410 | TP to TS 38.174 v0.0.1: RRC re-direction requirements for IAB MT | Ericsson |
| R4-2004807 | RRC Connection Mobility Control in IAB Networks | Qualcomm |
| R4-2004841 | RRC connection control for IAB MTs | ZTE Corporation |
| 6.5.3.3 | MT timing related requirements [NR_IAB-Core] | |
| R4-2004250 | TP to TS 38.174 on transmit timing requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004251 | TP to TS 38.174 on timing advance requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004840 | MT timing requirements for IAB | ZTE Corporation |
| 6.5.3.4 | RLM requirements [NR_IAB-Core] | |
| R4-2003532 | Discussion on RLM requirement for IAB-MT | Samsung |
| R4-2004248 | Discussion on RLM requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004806 | IAB-MT RLM requirements | Qualcomm |
| R4-2004837 | on RLM requirements for IAB MT | ZTE Corporation |
| R4-2004838 | TP for IAB RLM | ZTE Corporation |
| 6.5.3.5 | BFR requirements [NR_IAB-Core] | |
| R4-2003533 | Discussion on BFR requirement for IAB-MT | Samsung |
| R4-2003534 | TP to TS 38.174 v0.0.1: Beam Candidate Detection Requirements for IAB MT | Samsung |
| R4-2004249 | Discussion on BFR requirement for IAB-MT | Huawei, Hisilicon |
| R4-2004803 | IAB-MT Link Recovery requirements | Qualcomm |
| R4-2004839 | on BFD and BFR requirements for IAB MT | ZTE Corporation |
| 6.5.4 | EMC core requirements [NR_IAB-Core] | |
| R4-2004090 | [IAB EMC]further discussion on IAB EMC emission requirement | ZTE Corporation |
| R4-2004091 | [IAB EMC]further discussion on IAB EMC immunity requirement | ZTE Corporation |
| R4-2004092 | [IAB EMC]on how to handle IAB EMC | ZTE Corporation |
| R4-2004093 | [IAB EMC]TP to TR IAB EMC emission requirements | ZTE Corporation |
| R4-2004094 | [IAB EMC]TP to TR IAB EMC General part | ZTE Corporation |
| R4-2004095 | [IAB EMC]TP to TR IAB EMC immunity requirements | ZTE Corporation |
| 6.6.1 | General [LTE_NR_DC_CA_enh-Core] | |
| R4-2003783 | Handling new added channel bandwidth in NR CA configuration | ZTE Corporation |
| R4-2003784 | Handling the inter-band NR DC configurations | ZTE Corporation |
| 6.6.2 | RF requirements [LTE_NR_DC_CA_enh-Core] | |
| R4-2003418 | A discussion about current NR-DC FR1+FR1 situation in RAN4 | T-Mobile USA Inc. |
| R4-2003782 | Discussion on inter-band NR FR1+FR1 DC requirement | ZTE Corporation |
| R4-2003785 | Draft CR to TS38.101-1: Introduction of NR DC | ZTE Corporation |
| R4-2004058 | Discussion on the necessity of p-UE-FR2 | vivo, Intel |
| R4-2004059 | Draft Reply LS on power control for NR-DC | vivo |
| R4-2004214 | Introduction of requirements for NR-DC | Ericsson |
| R4-2004215 | Introduction of requirements for NR-DC | Ericsson |
| 6.6.3.2 | Early Measurement reporting [LTE_NR_DC_CA_enh-Core] | |
| R4-2004208 | Reply LS on clarification of UE requirements for early measurement performance and reporting | ZTE |
| R4-2004209 | Discussion on clarification of UE requirements for early measurement performance and reporting | ZTE |
| R4-2004654 | On measurement capability for EMR | Ericsson |
| R4-2004655 | Response LS on clarification of UE requirements for early measurement performance and reporting | Ericsson |
| R4-2004883 | Early measurement reporting in MR-DC | Qualcomm Incorporated |
| 6.6.3.2.1 | NR measurements for EMR [LTE_NR_DC_CA_enh-Core] | |
| R4-2003601 | Discussion on LTE CRS based and NR SSB based measurement in NR IDLE/INACTIVE mode | MediaTek inc. |
| R4-2003602 | CR on TS38.133 for measurement capability when early measurement reporting is supported (Section 4.2.2.1) | MediaTek inc. |
| R4-2003976 | On NR Measurement for EMR | OPPO |
| R4-2004351 | Discussion on early measurement in NR | Huawei, HiSilicon |
| R4-2004439 | NR MR-DC RRM requirements | Nokia, Nokia Shanghai Bell |
| R4-2004440 | TP for NR MR-DC RRM requirements | Nokia, Nokia Shanghai Bell |
| R4-2004441 | Big CR Introduction of UE requirement for MR-DC early measurement reporting in 38.133 | Nokia, Nokia Shanghai Bell |
| 6.6.3.2.2 | LTE NR Inter-RAT EMR | |
| R4-2003603 | Discussion on NR SSB based measurement in LTE IDLE/INACTIVE mode | MediaTek inc. |
| R4-2004352 | Discussion on LTE – NR inter-RAT EMR | Huawei, HiSilicon |
| R4-2004442 | NR EMR requirements for 36.133 | Nokia, Nokia Shanghai Bell |
| R4-2004443 | Text Proposal for NR EMR requirements for 36.133 | Nokia, Nokia Shanghai Bell |
| R4-2004444 | Big CR Introduction of UE requirement for MR-DC early measurement reporting in 36.133 | Nokia, Nokia Shanghai Bell |
| 6.6.3.3.1 | Direct SCell activation [LTE_NR_DC_CA_enh-Core] | |
| R4-2004353 | CR on interruption requirements for direct SCell activation for 38.133 | Huawei, HiSilicon |
| R4-2004354 | CR on interruption requirements for direct SCell activation for 36.133 | Huawei, HiSilicon |
| R4-2004420 | On Direct SCell Activation | Ericsson |
| R4-2004421 | Draft CR 38.133 (8.3.4-5) Corrections to Direct SCell Activation | Ericsson |
| R4-2004851 | On delay requirements for direct SCell activation in resume | ZTE Corporation |
| R4-2004852 | [CR] Add delay requirements for direct SCell activation in resume | ZTE Corporation |
| R4-2004853 | [CR] Delay requirements for direct SCell activation | ZTE Corporation |
| 6.6.3.3.2 | SCell dormancy [LTE_NR_DC_CA_enh-Core] | |
| R4-2003359 | Considerations on Scell domancy RRM requirements | vivo |
| R4-2003382 | Considerations on Scell domancy RRM requirements | vivo |
| R4-2003593 | On dormant BWP configuration and related operation | Futurewei Technologies |
| R4-2003604 | Discussion on dormancy Scell | MediaTek inc. |
| R4-2003960 | Discussion on RRM requirements for SCell dormancy | NEC |
| R4-2004355 | Discussion on SCell dormancy | Huawei, HiSilicon |
| R4-2004356 | CR on delay requirements for SCell dormancy | Huawei, HiSilicon |
| R4-2004422 | On SCell Dormancy Switching Delay | Ericsson |
| R4-2004445 | SCell Dormancy requirements discussion | Nokia, Nokia Shanghai Bell |
| R4-2004884 | Scell BWP dormancy | Qualcomm Incorporated |
| 6.7.2 | RRM core requirements (38.133) [NR_UE_pow_sav-Core] | |
| R4-2004061 | Correction on RRC parameter referenced for MIMO layer adaptation | vivo, CATT |
| 6.7.2.1 | RRM measurement relaxation [NR_UE_pow_sav-Core] | |
| R4-2003250 | Discussion on the remaining issues for RRM measurement relaxation | CATT |
| R4-2003251 | Reply LS to RAN2 on RRM measurement relaxation in power saving | CATT |
| R4-2003252 | Draft CR on measurement relaxation in IDLE mode for UE power saving | CATT |
| R4-2003253 | Draft CR for DCI based TCI state switch delay due to cross slot scheduling | CATT |
| R4-2003254 | Draft CR for DCI based BWP switch delay due to cross slot scheduling | CATT |
| R4-2003341 | Measurement relaxation for power saving | LG Electronics Inc. |
| R4-2003342 | LS on measurement relaxatino for inter-frequency on power saving | LG Electronics Inc. |
| R4-2003352 | Further discussion on remaining issues on NR UE power savings | vivo |
| R4-2003353 | Discussion on scaling factor and transition period for RRM relaxation on NR UE power savings | vivo |
| R4-2003354 | LS on RRM relaxation for higher priority inter frequency layer | vivo |
| R4-2003355 | LS on introducing thresholds for inter-frequency RRM relaxation for UE Power Saving | vivo |
| R4-2003375 | Further discussion on remaining issues on NR UE power savings | vivo |
| R4-2003376 | Discussion on scaling factor and transition period for RRM relaxation on NR UE power savings | vivo |
| R4-2003377 | LS on RRM relaxation for higher priority inter frequency layer | vivo |
| R4-2003378 | LS on introducing thresholds for inter-frequency RRM relaxation for UE Power Saving | vivo |
| R4-2003522 | RRM measurement relaxation for UE power saving | CMCC |
| R4-2003600 | Discussion on RRM measurement relaxation in IDLE/INACTIVE mode | MediaTek inc. |
| R4-2003820 | Draft CR on IDLE state intra-frequency measurement relaxation for UE power saving | vivo |
| R4-2003977 | Further discussion on RRM measurement relaxation for power saving | OPPO |
| R4-2004191 | Discussions on RRM impact of NR UE power saving | Ericsson |
| R4-2004192 | Reply LS on RRM relaxation in power saving | Ericsson |
| R4-2004288 | Discussion on measurement relaxation in power saving | Huawei, Hisilicon |
| R4-2004289 | [Draft] LS reply on RRM relaxation in power saving | Huawei, Hisilicon |
| R4-2004446 | RRM requirements for UE Power Saving | Nokia, Nokia Shanghai Bell |
| R4-2004447 | LS on introduction of carrier specific thresholds for UE Power Saving schemes | Nokia, Nokia Shanghai Bell |
| R4-2004448 | Higher Priority carriers and UE power saving LS | Nokia, Nokia Shanghai Bell |
| R4-2004449 | LS to RAN2 on RRM relaxation in power saving | Nokia, Nokia Shanghai Bell |
| R4-2004805 | RRM measurement relaxation for power saving | Qualcomm |
| 6.7.3 | Demodulation and CSI requirements (38.101-4) [NR_UE_pow_sav-Perf] | |
| R4-2003284 | Discussion on Demodulation requirement for power saving | CATT |
| R4-2003405 | On demod test case with MIMO layer adaptation | Apple |
| R4-2003523 | Demodulation on UE power saving | CMCC |
| R4-2003708 | Discussion on the performance requirements for NR power saving | Huawei, HiSilicon |
| R4-2003740 | Discussion on per BWP max MIMO layer adaptation for power saving | Huawei, HiSilicon |
| R4-2003747 | Discussion on the performance requirements for NR power saving | Huawei, HiSilicon |
| R4-2003848 | Discussion on 4Rx demod requirement impact due to MIMO layer adaptation | vivo |
| R4-2003855 | View on UE demodulation requirements considering cross-slot scheduling | NTT DOCOMO, INC. |
| R4-2004804 | Impact of MIMO layer adaptation on demod requirements | Qualcomm |
| 6.8.2.1 | UE requirements | |
| R4-2003294 | LS on UE measurement report mapping | CATT |
| R4-2003296 | Reply LS to RAN2 on measurement range and granularity | CATT |
| R4-2003512 | Discussion on general aspects of UE measurement for NR POS | MediaTek inc. |
| R4-2004357 | [draft] LS on report mapping for UE positioning measurement | Huawei, HiSilicon |
| R4-2004673 | Response LS on measurement range and granularity | Ericsson |
| R4-2004674 | LS on UE measurement report mapping for UE positioning measurements in NR | Ericsson |
| R4-2004678 | On additional path reporting with positioning measurements | Ericsson |
| R4-2004679 | On new measurement gaps for NR positioning | Ericsson |
| 6.8.2.1.1 | PRS-RSTD measurements | |
| R4-2003207 | Further Discussion on NR PRS RSTD Requirements for UE | Intel Corporation |
| R4-2003285 | Discussion on RSTD measurement requirements | CATT |
| R4-2003290 | draft CR on RSTD measurement period | CATT |
| R4-2003292 | draft CR on RSTD measurement report mapping | CATT |
| R4-2003401 | On remaining issues of NR RSTD measurement report mapping | Apple |
| R4-2003402 | LS on RSTD measurement report mapping for NR positioning | Apple |
| R4-2003508 | Discussion on PRS-RSTD measurement | MediaTek inc. |
| R4-2003567 | On PRS-RSTD measurements for NR positioning | Qualcomm Incorporated |
| R4-2004358 | Discussion on RSTD measurement | Huawei, HiSilicon |
| R4-2004667 | On PRS RSTD measurements | Ericsson |
| R4-2004668 | On PRS RSTD measurement report mapping | Ericsson |
| R4-2004669 | Measurement report mapping for PRS RSTD | Ericsson |
| R4-2004970 | PRS-RSTD measurements for NR positioning | ZTE Corporation |
| 6.8.2.1.2 | PRS-RSRP measurements | |
| R4-2003286 | Discussion on PRS-RSRP measurement requirements | CATT |
| R4-2003291 | draft CR on PRS-RSRP measurement period | CATT |
| R4-2003509 | Discussion on PRS-RSRP measurement | MediaTek inc. |
| R4-2003568 | On PRS-RSRP measurements for NR positioning | Qualcomm Incorporated |
| R4-2004359 | Discussion on PRS-RSRP measurement | Huawei, HiSilicon |
| R4-2004670 | On PRS-RSRP measurements | Ericsson |
| R4-2004671 | On PRS-RSRP measurement report mapping | Ericsson |
| R4-2004672 | Measurement report mapping for PRS-RSRP | Ericsson |
| 6.8.2.1.3 | Rx-Tx time difference measurements [NR_pos-Core] | |
| R4-2003293 | draft CR on UE Rx-Tx time difference measurement report mapping | CATT |
| R4-2003297 | draft CR on UE Rx-Tx time difference measurement period | CATT |
| R4-2003298 | Discussion on UE Rx-Tx time difference measurement requirements | CATT |
| R4-2003510 | Discussion on UE Rx-Tx time difference measurements | MediaTek inc. |
| R4-2003569 | On UE Rx-Tx time difference measurement for NR positioning | Qualcomm Incorporated |
| R4-2004360 | Discussion on Rx-Tx time difference measurement | Huawei, HiSilicon |
| R4-2004411 | UE Rx-Tx Measurement Report Mapping in NR | Ericsson |
| R4-2004666 | On UE Rx-Tx measurements | Ericsson |
| 6.8.2.1.4 | SSB and CSI-RS RSRP/RSRQ measurements | |
| R4-2003570 | On including SINR measurements in E-CID | Qualcomm Incorporated |
| R4-2004675 | NR E-CID reporting criteria requirements | Ericsson |
| R4-2004676 | LS on NR E-CID measurements | Ericsson |
| R4-2004677 | NR E-CID measurement requirements | Ericsson |
| 6.8.2.1.5 | Link-level evaluations for PRS-RSTD and PRS-RSRP [NR_pos-Core] | |
| R4-2003209 | Link-level simulation results for RSTD measurement | Intel Corporation |
| R4-2003288 | Updated link level simulation results of RSTD measurement | CATT |
| R4-2003289 | Updated link level simulation results of PRS-RSRP measurement | CATT |
| R4-2003511 | Link level evaluation on PRS-RSRP and PRS-RSTD | MediaTek inc. |
| R4-2003571 | Link-level PRS-RSTD simulation results | Qualcomm Incorporated |
| R4-2004361 | Link level simulation results for RSTD measurement | Huawei, HiSilicon |
| R4-2004362 | Link level simulation results for PRS-RSRP measurement | Huawei, HiSilicon |
| R4-2004665 | Updated link simulation results for NR RSTD | Ericsson |
| 6.8.2.2 | Impact on existing RRM requirements [NR_pos-Core] | |
| R4-2003206 | Discussion on UE RRM impacts due to NR Pos measurement | Intel Corporation |
| R4-2003299 | Impact on existing RRM measurement | CATT |
| R4-2003573 | On Impact of NR positioning on existing RRM requirements | Qualcomm Incorporated |
| R4-2003849 | Discussion on gap pattern configuration for NR positioning | vivo |
| R4-2004366 | Impact of positioning on existing RRM requirements | Huawei, HiSilicon |
| R4-2004367 | [draft] LS on measurement gap for PRS measurement | Huawei, HiSilicon |
| R4-2004412 | Impact of active BWP change on positioning measurements | Ericsson |
| 6.8.2.3 | gNB requirements [NR_pos-Core] | |
| R4-2003208 | Considerations on gNB measurement report mapping | Intel Corporation |
| R4-2003287 | Discussion on gNB measurement requirement and report mapping | CATT |
| R4-2003295 | LS on gNB measurement report mapping | CATT |
| R4-2003546 | draft CR on UL RTOA measurement report mapping | CATT |
| R4-2003547 | draft CR on gNB Rx-Tx time difference measurement report mapping | CATT |
| R4-2003548 | draft CR on SRS RSRP time difference measurement report mapping | CATT |
| R4-2003572 | on gNB requirements for NR positioning | Qualcomm Incorporated |
| R4-2004002 | Optionality for positioning measurements in gNB | Ericsson LM |
| R4-2004011 | BS measurements reporting mapping for gNB Rx-Tx, SRS-RSRP and UL RTOA | Ericsson LM |
| R4-2004012 | Scenarios for gNB Rx-Tx and SRS-RSRP measurements for BS | Ericsson LM |
| R4-2004036 | Feasibility of UL RTOA and AoA measurements for BS | Ericsson LM |
| R4-2004078 | On gNB measurement accuracy requirements for NR positioning | Nokia, Nokia Shanghai Bell |
| R4-2004079 | On gNB measurement report mapping for NR positioning | Nokia, Nokia Shanghai Bell |
| R4-2004363 | Discussion on the scope gNB requirements for NR positioning | Huawei, HiSilicon, CMCC |
| R4-2004364 | Discussion on gNB positioning measurement requirements and report mapping | Huawei, HiSilicon |
| R4-2004365 | [draft] LS on report mapping for gNB positioning measurement | Huawei, HiSilicon |
| R4-2004969 | gNB requirements for NR positioning | ZTE Corporation |
| 6.8.2.4 | Others [NR_pos-Core] | |
| R4-2003210 | [draft] Reply LS on NR Positioning measurement report range and granularity | Intel Corporation |
| R4-2004080 | UE behaviour for processing DL PRS without measurement gap | Nokia, Nokia Shanghai Bell |
| 6.9.1 | emodulation and CSI requirements | |
| R4-2003845 | On FR1 and FR2 for URLLC | Ericsson |
| 6.9.1.1 | Test feasibility [NR_L1enh_URLLC-Perf] | |
| R4-2003181 | Discussion on test method and requirements for Ultra-low BLER | Intel Corporation |
| R4-2003678 | Discussion on URLLC high reliability test feasibility | Huawei, HiSilicon |
| R4-2003842 | URLLC ultra-low BLER test | Ericsson |
| R4-2003900 | On NR Rel-16 high reliability BS demodulation test feasibility and methodology | Nokia, Nokia Shanghai Bell |
| R4-2003901 | On NR Rel-16 relaxed high reliability and low latency BS demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2004557 | Views on URLLC Test Feasibility | Qualcomm Incorporated |
| 6.9.1.2 | UE demodulation and CSI requirements (38.101-4) | |
| R4-2003182 | Discussion on UE performance requirements for URLLC | Intel Corporation |
| R4-2003679 | Discussion and simulation for URLLC UE PDSCH demodulation requirements for high reliability | Huawei, HiSilicon |
| R4-2003680 | Discussion on URLLC UE performance requirements for low latency for verifying pre-emption | Huawei, HiSilicon |
| R4-2003681 | Discussion and simulation on URLLC UE performance requirements for verifying PDSCH mapping Type B and processing capabiltiy 2 | Huawei, HiSilicon |
| R4-2003682 | Discussion on URLLC UE CQI reporting requirements | Huawei, HiSilicon |
| R4-2004010 | Views on UE demodulation requirements for URLLC | NTT DOCOMO, INC. |
| R4-2004781 | Views on URLLC Test Cases | Qualcomm Incorporated |
| 6.9.1.3 | BS demodulation requirements (38.104) [NR_L1enh_URLLC-Perf] | |
| R4-2003183 | Discussion on BS performance requirements for URLLC | Intel Corporation |
| R4-2003631 | Views on NR BS performance for URLLC | NTT DOCOMO, INC. |
| R4-2003683 | Discussion and simulation for URLLC BS PUSCH demodulation requirements for high reliability | Huawei, HiSilicon |
| R4-2003684 | Discussion and simulation on URLLC BS performance requirements for low latency | Huawei, HiSilicon |
| R4-2003826 | Discussion on CQI reporting requirements for URLLC | Ericsson |
| R4-2003827 | Discussion on pre-emption indication | Ericsson |
| R4-2003828 | Views on UE URLLC performance requirements for Slot Aggregation | Ericsson |
| R4-2003829 | Views on UE URLLC performance requirements for Type B and PDSCH capability 2 | Ericsson |
| R4-2003843 | URLLC BS reliability related requirement | Ericsson |
| R4-2003844 | URLLC BS latency related requirement | Ericsson |
| R4-2004919 | View on BS demodulation requirement for URLLC in NR Rel-16 | Samsung |
| 6.10.1 | RRM core requirements maintenance (38.133) [SRVCC_NR_to_UMTS-Core] | |
| R4-2003097 | Correction to gap applicability with SRVCC | Ericsson |
| 6.10.2 | RRM perf requirements (38.133) [SRVCC_NR_to_UMTS-Perf] | |
| R4-2003096 | Event triggered reporting test for WCDMA measurements in NR FR1 | Ericsson |
| R4-2004307 | Test case for NR to UTRA FDD Inter-RAT handover | Huawei, Hisilicon |
| 6.11.1 | UE RF core requirements (38.101) [NR_eMIMO-Core] | |
| R4-2004964 | Draft CR to add PC3 UL-MIMO bands | CMCC |
| 6.11.1.1 | DMRS enhancement with PI/2 BPSK [NR_eMIMO-Core] | |
| R4-2004473 | Pi_2 BPSK DMRS | Qualcomm Incorporated |
| R4-2004737 | On Pi/2 BPSK DMRS evaluation | Huawei, HiSilicon |
| 6.11.1.2 | Uplink Tx Full Power transmission [NR_eMIMO-Core] | |
| R4-2003216 | On eMIMO full Tx power transmission | Intel Corporation |
| R4-2003217 | On Transparent Tx Diversity | Intel Corporation |
| R4-2003330 | Consideration on introduction of Tx diversity feature in Rel-16 | Anritsu Corp. |
| R4-2003537 | Further Discussion on Uplink Tx Full Power Transmission | Samsung |
| R4-2003874 | FP transmission, transparent TxD and additional power-class capability | Ericsson |
| R4-2003907 | Further on full power transmission in eMIMO | OPPO |
| R4-2004056 | Further discussion on UE RF requirments for eMIMO UL Full power Tx | vivo |
| R4-2004474 | TX full power capability | Qualcomm Incorporated |
| R4-2004738 | On NR eMIMO full power transmission | Huawei, HiSilicon |
| R4-2004869 | Full power transmission and FR2 | Qualcomm Incorporated |
| R4-2004977 | Enabling TX diversity for eMIMO | Qualcomm Incorporated |
| 6.11.2.1 | L1-SINR [NR_eMIMO-Core] | |
| R4-2003201 | Discussion about L1-SINR measurement requirements | Intel Corporation |
| R4-2003538 | On the Remaining Issues for L1-SINR Measurement Requirement | Samsung |
| R4-2003539 | Draft CR to TS38.133 on L1-SINR Measurement Requirement (Section 3.3 and 9) | Samsung |
| R4-2003540 | Simulation Results Summary for L1-SINR Measurement Accuracy | Samsung |
| R4-2003621 | Discussion on RRM requirements for L1-SINR | MediaTek inc. |
| R4-2004321 | Discussion on L1-SINR measurement requirements for NR eMIMO | Huawei, HiSilicon |
| R4-2004322 | DraftCR on L1-SINR measurement for reporting | Huawei, HiSilicon |
| R4-2004323 | Discussion on L1-SINR accuracy requirements for NR eMIMO | Huawei, HiSilicon |
| R4-2004324 | Simulation results of L1-SINR measurements for NR eMIMO | Huawei, HiSilicon |
| R4-2004391 | Discussions on L1-SINR measurements for Rel-16 NR eMIMO | Nokia, Nokia Shanghai Bell |
| R4-2004799 | RRM requirements for L1-SINR estimation | Qualcomm |
| 6.11.2.2 | SCell Beam failure recovery [NR_eMIMO-Core] | |
| R4-2003541 | On the Remaining Issues for SCell Beam Failure Recovery RRM Requirement | Samsung |
| R4-2003542 | Draft CR to TS38.133 on SCell BFD and CBD (Section 8.5) | Samsung |
| R4-2003543 | Draft CR to TS38.133 on SCell BFRQ Procedure (Section 8.5) | Samsung |
| R4-2003622 | Discussion on RRM requirements for BFR on Scell | MediaTek inc. |
| R4-2004023 | BFRQ on SR-like PUCCH resource | Ericsson |
| R4-2004325 | Discussion on SCell BFR requiremetns for NR eMIMO | Huawei, HiSilicon |
| R4-2004326 | DraftCR on SCell link recovery requirements | Huawei, HiSilicon |
| R4-2004800 | SCell Beam Failure Detection and Recovery | Qualcomm |
| 6.11.2.4 | Others | |
| R4-2003544 | Discussion on Multi-TRP/Panel Transmission on MRTD/MTTD | Samsung |
| R4-2003623 | Discussion on MRTD for multiple TRPs scenario | MediaTek inc. |
| 6.11.3.1 | General [NR_eMIMO-Perf] | |
| R4-2003424 | Views on test cases for eMIMO | Qualcomm Incorporated |
| R4-2003636 | Overview on test scope of Rel-16 eMIMO performance requirements | Samsung |
| 6.11.3.2 | Demodulation requirements [NR_eMIMO-Perf] | |
| R4-2003192 | Views on demodulation requirements for Rel-16 NR eMIMO | Intel Corporation |
| R4-2003685 | Discussion on PDSCH performance requirements for multi-DCI based multi-TRP transmission | Huawei, HiSilicon |
| R4-2003686 | Discussion on open issues for NR eMIMO | Huawei, HiSilicon |
| R4-2003885 | Test case design for DL multi-TRP/panel transmission | Samsung |
| R4-2004024 | Multi-TRP/Panel PDSCH requirements for eMBB | Ericsson |
| R4-2004025 | Multi-TRP/Panel PDSCH requirements for URLLC | Ericsson |
| R4-2004026 | PDSCH requirements with Rel-16 DMRS sequence | Ericsson |
| R4-2004923 | View on performance requirements for Rel-16 DMRS enhancement | Samsung |
| R4-2004924 | View on performance requirements for URLLC enhancement with multi-TRP/panel transmission | Samsung |
| R4-2004925 | Initial simulation results for PDSCH test cases with multi-TRP/panel transmission | Samsung |
| R4-2004928 | Test case design for DL multi-TRP/panel transmission | Samsung |
| 6.11.3.3 | CSI requirements [NR_eMIMO-Perf] | |
| R4-2003687 | Discussion on PMI reporting test for NR eMIMO | Huawei, HiSilicon |
| R4-2003825 | Discussion on CSI – PMI reporting requirements for Enhanced Type II Codebook | Ericsson |
| R4-2004926 | Initial simulation results for PMI requirement with Rel-16 enhanced type II codebook | Samsung |
| R4-2004927 | Test case design for Rel-16 enhanced type II codebook | Samsung |
| 6.12.1 | General (Ad-hoc MoM/TR maintenance) [NR_DL256QAM_FR2] | |
| R4-2003656 | Draft TR 38.883 for FR2 DL 256QAM v1.2.0 | China Telecom |
| 6.12.2 | BS RF core requirements (38.104) [NR_DL256QAM_FR2] | |
| R4-2003773 | Draft CR to TS 38.104: Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile, Ericsson |
| 6.12.3 | UE RF core requirements (38.101-2) [NR_DL256QAM_FR2] | |
| R4-2003625 | NR UE maximum input level for FR2 DL 256QAM | NTT DOCOMO, INC. |
| R4-2003657 | Maximum input level for FR2 DL 64QAM and 256QAM | China Telecom |
| R4-2003658 | TP for TR 38.883 UE RF requirements for FR2 DL 256QAM | China Telecom |
| R4-2003771 | UE RF core requirements for FR2 DL 256QAM | Nokia, Nokia Shanghai Bell |
| R4-2003772 | Draft CR to TS 38.101-2: Introduction of FR2 DL 256QAM | Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
| R4-2003908 | UE maximum input level for FR2 DL 256QAM | OPPO |
| R4-2004485 | UE maximum input level for DL 256QAM | Huawei, HiSilicon |
| 6.12.4 | Demodulation and CSI requirements (38.101-4) [NR_DL256QAM_FR2-Perf] | |
| R4-2003184 | Discussion on UE performance requirements for FR2 DL 256QAM | Intel Corporation |
| R4-2003707 | Discussion on the performance requirements for NR DL 256QAM FR2 | Huawei, HiSilicon |
| R4-2003746 | Discussion on the performance requirements for NR DL 256QAM FR2 | Huawei, HiSilicon |
| R4-2004007 | Views on DL 256QAM requirements for FR2 | NTT DOCOMO, INC. |
| R4-2004904 | Work plan for FR2 DL 256QAM demodulation and CSI reporting requirements | China Telecom |
| R4-2004905 | UE demodulation and CSI reporting requirements for FR2 DL 256QAM | China Telecom |
| 6.13.1 | RF core requirements [NR_RF_FR1] | |
| R4-2004387 | OOB blocking for n70 adjacent to n25 | Qualcomm Incorporated |
| R4-2004397 | OOB blocking for n91-n94 shared band with n75 and n76 | Qualcomm Incorporated |
| R4-2004399 | OOB blocking for Inter-band CA | Qualcomm Incorporated |
| R4-2004956 | Include band list for UL MIMO and n48 | Verizon UK Ltd |
| 6.13.1.1 | Almost contiguous allocations for CP-OFDM UL for FR1 [NR_RF_FR1] | |
| R4-2004401 | IBE requirement for almost contiguous allocations | Qualcomm Incorporated |
| 6.13.1.2 | Intra-band contiguous DL CA for FR1 [NR_RF_FR1] | |
| R4-2004428 | FR1 Intra-band DLCA ACS IBB and Wideband Intermodulation | Qualcomm Incorporated |
| R4-2004462 | FR1 Intra-band CA ACS IBB and WB IMD | Qualcomm Incorporated |
| R4-2004757 | CR for 38.101-1 DL RF requirement correction | Huawei, HiSilicon |
| 6.13.1.3 | Intra-band contiguous UL CA for FR1 power class 3 [NR_RF_FR1] | |
| R4-2003236 | Sub-block edges and ACLR MBW for FR1 contiguous UL CA | Nokia, Nokia Shanghai Bell, Skyworks Solutions Inc. |
| R4-2003781 | Discussion on NR CA aggregated channel bandwidth and ACLR MBW | ZTE Corporation |
| R4-2003786 | Draft CR to TS38.101-1_Correction on Aggregated channnel bandwidth | ZTE Corporation |
| R4-2003787 | Draft CR to TS38.101-2_Correction on Aggregated channnel bandwidth | ZTE Corporation |
| R4-2004475 | FR1 Intraband Contiguous ULCA | Qualcomm Incorporated |
| R4-2004750 | on FR1 UL CA MPR requirement Rel-16 | Huawei, HiSilicon |
| R4-2004751 | How to align Foffset for gNB and UE | Huawei, HiSilicon |
| R4-2004753 | CR on FR1 UL contiguous CA requirement | Huawei, HiSilicon |
| R4-2004782 | on FR1 UL contiguous CA emission requirement | Huawei, HiSilicon |
| 6.13.1.4 | Intra-band non-contiguous UL CA for FR1 power class 3 [NR_RF_FR1] | |
| R4-2004467 | FR1 Intra-band Non-contiguous ULCA | Qualcomm Incorporated |
| R4-2004766 | CR for intra-band UL non-contiguous CA requirement | Huawei, HiSilicon |
| 6.13.1.5 | Switching period between case 1 and case 2 [NR_RF_FR1] | |
| R4-2003321 | On open iussue for Tx switching between Case 1 and Case 2 | CATT |
| R4-2003338 | Switching between case 1 and case 2 for two NR FR1 carriers | Nokia, Nokia Shanghai Bell |
| R4-2003339 | draft CR to TS 38.101-1: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band UL CA and SUL case | Nokia, Nokia Shanghai Bell |
| R4-2003340 | draft CR to TS 38.101-3: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band EN-DC without SUL | Nokia, Nokia Shanghai Bell |
| R4-2003515 | Requirements for switching between case1 and case2 | CMCC |
| R4-2003909 | Further clarification on the power class between case1 and case2 | OPPO |
| R4-2003953 | Further discussion on Tx switching between two uplink carriers | ZTE Wistron Telecom AB |
| R4-2003986 | Switching time between NR between FR1 uplink carriers | MediaTek Inc. |
| R4-2004892 | RF issues for Tx switching between two uplink carriers | China Telecom |
| R4-2004893 | Draft CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL | China Telecom |
| R4-2004894 | Draft CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC | China Telecom |
| R4-2004895 | LS on DL interruption due to Tx switching | China Telecom |
| R4-2005020 | Views on the DL interruptions due to UE switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2005021 | LS on DL interruptions due to UE switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2005022 | draftCR to 38101-1 on switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| R4-2005023 | draftCR to 38101-3 on switching between 1Tx carrier and 2Tx carrier | Huawei, HiSilicon |
| 6.13.1.6 | Transient period capability [NR_RF_FR1] | |
| R4-2003331 | Consideration on testability issues for on-to-on transient period | Anritsu Corp. |
| R4-2004057 | Discussion on values for transient period capability | vivo |
| R4-2004132 | UE transient time capability | Ericsson |
| R4-2004719 | Testability of reported transient durations | Qualcomm Incorporated |
| R4-2004720 | Transient Period Capability in NR using existing window definitions | Qualcomm Incorporated |
| R4-2004721 | Transient Period Capability in NR using a new window definition | Qualcomm Incorporated |
| R4-2004752 | On transient period UE capability | Huawei, HiSilicon |
| 6.13.1.7 | Time masks for ULSUP-TDM in case of UL timing misalignment [NR_RF_FR1] | |
| R4-2003733 | Time masks for ULSUP in R16 | Huawei, HiSilicon |
| R4-2003734 | Draft CR to 38.101-3 on time masks for ULSUP in R16 | Huawei, HiSilicon |
| R4-2003875 | UE behavior and time masks for ULSUP-TDM | Ericsson |
| 6.13.2.1 | RRM requirements for Tx switching between two uplink carriers | |
| R4-2003516 | RRM requirements for switching between case1 and case 2 | CMCC |
| R4-2003642 | Interruption for Tx switching between two uplink carriers | MediaTek inc. |
| R4-2003764 | Draft CR on DL interruption on LTE carriers at Tx switching between two uplink carriers | Huawei, HiSilicon |
| R4-2003978 | On RRM requirements for Tx switching between two uplink carriers | OPPO |
| R4-2004896 | View on RRM interruption requirement for switching between two uplink carriers | China Telecom |
| R4-2005024 | DL interruption due to Tx switching between two uplink carriers | Huawei, HiSilicon |
| R4-2005025 | draftCR on DL interruption Tx switching between two uplink carriers | Huawei, HiSilicon |
| 6.14.1.1 | FR2 MPE [NR_RF_FR2_req_enh] | |
| R4-2003231 | Discussion on enhancement of MPE in Rel-16 on FR2 | LG Electronics France |
| R4-2003333 | UE FR2 MPE enhancements and solutions | Nokia, Nokia Shanghai Bell |
| R4-2003334 | [Draft] LS on MPE enhancements | Nokia, Nokia Shanghai Bell |
| R4-2003344 | Remaining issues for Rel-16 signaling solution | Intel Corporation |
| R4-2003346 | P-MPR reporting and UE behavior for MPE enhancement | Sony, Ericsson |
| R4-2003779 | Enhancement on FR2 MPE mitigation | ZTE Corporation |
| R4-2003910 | Further on MPE enhancement | OPPO |
| R4-2003911 | [Draft] LS on MPE enhancement | OPPO |
| R4-2004060 | Discussion on FR2 MPE mitigation | vivo |
| R4-2004684 | Further considerations on the uplink duty cycle enhancements for the MPE scenario | Apple Inc. |
| R4-2004770 | On MPE enhancement_FR2 | Huawei, HiSilicon |
| R4-2004937 | Remaining details for MPE solution | InterDigital Communications |
| R4-2004978 | Dynamic duty cycle for preventing MPE caused RLF | Qualcomm Incorporated |
| 6.14.1.2 | Beam Correspondence based on configured DL RS (SSB or CSI-RS) [NR_RF_FR2_req_enh] | |
| R4-2003213 | On SSB based Beam Correspondence | Intel Corporation |
| R4-2003232 | Discussion on enhancement of BC in Rel-16 at FR2 | LG Electronics France |
| R4-2003335 | FR2 Beam Correspondence enhancements | Nokia, Nokia Shanghai Bell |
| R4-2003347 | Enhanced reporting for beam correspondence in poor SNR condition | Sony |
| R4-2003348 | Views on SSB only beam correspondence | Sony, Ericsson |
| R4-2003409 | On SSB based beam correspondence | Apple |
| R4-2003468 | Views on beam correspondence enhancement based on SSB in Rel-16 | NTT DOCOMO, INC. |
| R4-2003876 | SSB/CSI-RS only and initial-access BC tests | Ericsson, Sony |
| R4-2003877 | Verification of beam correspondence during initial access | Ericsson, Sony |
| R4-2004710 | Remaining issues with beam correspondence in Rel-16 | Apple Inc. |
| R4-2004711 | TP to TR38.831: beam correspondence enhancement | Apple Inc. |
| R4-2004756 | On beam correspondence enhancement | Huawei, HiSilicon |
| R4-2004885 | On FR2 Initial access beam correspondence | Qualcomm Incorporated |
| R4-2004886 | FR2 Beam Correspondence using SSB only | Qualcomm Incorporated |
| R4-2004887 | Beam management CSI-RS design for BC requirement | Qualcomm Incorporated |
| R4-2004888 | Further enhancement of Beam Correspondence | Qualcomm Incorporated |
| R4-2004992 | Discussion on beam correspondence enhancement | Samsung |
| 6.14.1.3 | Intra-band non-cont DL CA for aggregated BW larger than 1400 MHz [NR_RF_FR2_req_enh] | |
| R4-2004696 | Peak EIS intra-band CA for FR2 | Apple Inc. |
| R4-2004697 | Draft CR to 38.101-2 on REFSENS for intra-band non-contiguous CA for FR2 | Apple Inc. |
| R4-2004698 | [draft] LS to RAN2 on DL-only separation class | Apple Inc. |
| R4-2004699 | Draft CR to 38.101-2 on FR2 frequency separation class enhancement | Apple Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2004714 | Views on radiative degradation mechanisms for larger frequency separation | Apple Inc. |
| R4-2004754 | On intra-band NC DL CA_FR2 | Huawei, HiSilicon |
| R4-2004797 | dCR to 38.101-2: DL CA BW Enhancement and CA REFSENS | Qualcomm India Pvt Ltd |
| R4-2004870 | FR2 DL Intra-band CA BW Enhancement Feature Completion | Qualcomm Incorporated |
| R4-2004871 | TP to TR38.831: FR2 UE architectures for DL Intra-band CA BW Enhancement | Qualcomm Incorporated |
| R4-2004872 | Beam squint analysis for FR2 UEs | Qualcomm Incorporated |
| R4-2004993 | Discussion on FR2 intra-band DL CA | Samsung |
| 6.14.1.4 | Intra-band non-contiguous UL CA [NR_RF_FR2_req_enh] | |
| R4-2004713 | Non-simultaneous UL for non-contiguous UL CA in FR2 | Apple Inc. |
| R4-2004755 | on beam squint cased degradation | Huawei, HiSilicon |
| R4-2004816 | FR2 Intra-Band Non-Contiguous UL CA Back-off Measurements | Skyworks Solutions Inc. |
| 6.14.1.5 | Inter-band DL CA [NR_RF_FR2_req_enh] | |
| R4-2003214 | PSD imbalance in Inter-band DL CA | Intel Corporation |
| R4-2003332 | Consideration on FR2 OTA test system with multi signal transmission | Anritsu Corp. |
| R4-2003349 | Preliminary analysis on beam squint due to larger frequency separation | Sony, Ericsson |
| R4-2003350 | Views on inter-band DL CA in FR2 for LB+HB | Sony, Ericsson |
| R4-2004062 | Discussion on test setups for inter-band CA in FR2 | Rohde & Schwarz |
| R4-2004695 | Peak EIS inter-band CA for FR2 | Apple Inc. |
| R4-2004700 | Views on PSD difference in FR2 | Apple Inc. |
| R4-2004715 | Common EIS CDF metric for inter-band CA | Apple Inc. |
| R4-2004768 | On inter band DL CA_FR2 | Huawei, HiSilicon |
| R4-2004814 | PSD difference on FR2 inter-band CA 28GHz+40GHz | NTT DOCOMO INC. |
| R4-2004880 | dCR to 38.101-2: Simultaneous NC UL CA framework for Rel-16 | Qualcomm Incorporated |
| R4-2004881 | On A-MPR for FR2 NC UL CA | Qualcomm Incorporated |
| R4-2004882 | On MPR for FR2 NC UL CA | Qualcomm Incorporated |
| R4-2004979 | Remaining requirements for inter-band CA | Qualcomm Incorporated |
| R4-2004980 | Inter-band CA with_without independent Rx beam | Qualcomm Incorporated |
| R4-2004981 | DraftCR on Introduction of inter-band CA to 38.101-2 | Qualcomm Incorporated |
| R4-2004994 | Discussion on FR2 inter-band CA | Samsung |
| 6.14.1.6 | Improvement of UE MPR | |
| R4-2003215 | FR2 CA MPR improvement | Intel Corporation |
| R4-2004873 | FR2 UE EIRP increase with IBE relaxation | Qualcomm Incorporated |
| R4-2004874 | LS on UL power boost mode and IBE relaxation | Qualcomm Incorporated |
| R4-2004875 | dCR to 38.101-2: FR2 UE EIRP increase with IBE relaxation | Qualcomm Incorporated |
| R4-2004999 | FR2 new MPR and modifiedmpr-signaling | Nokia, Nokia Shanghai Bell |
| 6.14.1.7 | Improvement of spherical coverage requirements for PC3 [NR_RF_FR2_req_enh] | |
| R4-2003343 | Discussion on spherical coverage improvement for PC3 | LG Electronics Inc. |
| R4-2003351 | Views on improvement to spherical coverage requirements for PC3 | Sony |
| R4-2003653 | Further view on spherical coverage improvement for Rel-16 | Samsung |
| R4-2004712 | Views on PC3 spherical coverage requirements in Rel-16 and beyond | Apple Inc. |
| R4-2004829 | Further discussion on Spherical coverage enhancement | NTT DOCOMO INC. |
| R4-2004989 | Further view on spherical coverage improvement for Rel-16 | Samsung |
| 6.14.1.8 | Multiband relaxation framework enhancement [NR_RF_FR2_req_enh] | |
| R4-2003654 | View on multi-band relaxation (MBR) framework | Samsung, Qualcomm |
| R4-2003655 | Draft CR to 38.101-2 on CR to 38.101-2: Revision to Multiband Relaxations | Samsung, Qualcomm |
| R4-2003858 | Multi-band relaxation framework | NTT DOCOMO INC. |
| R4-2003912 | Further on multi-band relaxation | OPPO |
| R4-2004213 | Multiband relaxation framework | Ericsson, Sony |
| R4-2004704 | Multi-band relaxation framework for FR2 in Rel-16 and beyond | Apple Inc. |
| R4-2004705 | [draft] LS response on Multiband relaxation for FR2 | Apple Inc. |
| R4-2004706 | Draft CR to 38.101-2 on correction of the FR2 multi-band requirement framework | Apple Inc. |
| R4-2004990 | View on multi-band relaxation (MBR) framework | Samsung |
| 6.14.2.1 | Inter-band DL CA MRTD [NR_RF_FR2_req_enh] | |
| R4-2003410 | On MRTD for inter-band FR2 CA with common and independent beam management | Apple |
| R4-2003416 | MRTD requirements for FR2 inter-band DL CA | Ericsson |
| R4-2003641 | MRTD requirements for FR2 inter-band DL CA | MediaTek inc. |
| R4-2004327 | Discussion on MRTD requirements for FR2 inter-band DL CA | Huawei, HiSilicon |
| R4-2004524 | MRTD for inter-band DL CA | Nokia, Nokia Shanghai Bell |
| 6.15.1.1 | SRS carrier switching requirements [NR_RRM_Enh-Core] | |
| R4-2003501 | Discussion on Interruption at SRS carrier switch | MediaTek inc. |
| R4-2003810 | Interruption requirements due to SRS carrier switching | Nokia, Nokia Shanghai Bell |
| R4-2003979 | Discussion on remaining issues for SRS carrier switching | OPPO |
| R4-2004108 | Remaining open issues on NR SRS carrier switching RRM requirements | ZTE |
| R4-2004109 | draft CR to 38.133 on SRS carrier switching interruption requirements | ZTE |
| R4-2004110 | draft CR to 36.133 on SRS carrier switching interruption requirements | ZTE |
| R4-2004298 | Discussion on SRS carrier switching interruption | Huawei, Hisilicon |
| R4-2004299 | CR on NR SRS carrier switching interruption in TS 36.133 | Huawei, Hisilicon |
| R4-2004300 | CR on impact on LTE RRM measurement due to NR SRS carrier switching | Huawei, Hisilicon |
| R4-2004786 | Further discussion on remaining issues in SRS carrier switching | Qualcomm Incorporated |
| 6.15.1.2 | Multiple Scell activation/deactivation [NR_RRM_Enh-Core] | |
| R4-2003403 | On remaining issues for activation delay extension due to multiple SCell activations | Apple |
| R4-2003404 | On activation delay requirements for multiple SCell activation | Apple |
| R4-2003502 | Discussion on Multiple SCell activation | MediaTek inc. |
| R4-2003811 | Multiple SCells Activation Delay Requirements | Nokia, Nokia Shanghai Bell |
| R4-2003961 | Discussion on remaining open issues in delay extension of multiple SCell activation | NEC |
| R4-2004368 | Discussion on multiple SCell activation | Huawei, HiSilicon |
| R4-2004423 | On Activation of Multiple SCells | Ericsson |
| R4-2004788 | Further discussion on multiple SCell activation in NR | Qualcomm Incorporated |
| 6.15.1.3 | CGI reading requirements with autonomous gap | |
| R4-2003103 | Further considerations for CGI decoding in NR | Ericsson |
| R4-2003104 | NR CGI measurements with autonomous gaps for 38.133 | Ericsson |
| R4-2003105 | NR CGI measurements with autonomous gaps for 36.133 | Ericsson |
| R4-2003503 | Discussion on CGI reading requirement for NR | MediaTek inc. |
| R4-2004104 | Further discussion on NR CGI reading with autonomous gaps | ZTE |
| R4-2004105 | draft CR to 38.133 on CGI reading of NR cell | ZTE |
| R4-2004106 | draft CR to 38.133 on interruption requirements for CGI reading | ZTE |
| R4-2004107 | Reply LS on CGI reading with autonomous gaps | ZTE |
| R4-2004369 | Discussion on NR CGI reading requirements | Huawei, HiSilicon |
| R4-2004370 | Discussion on LTE CGI reading requirements | Huawei, HiSilicon |
| R4-2004371 | CR to 36.133 on interruption requirements for CGI reading | Huawei, HiSilicon |
| R4-2004372 | CR to 36.133 on CGI reading of LTE cell | Huawei, HiSilicon |
| R4-2004516 | discussion on CGI reading with autonomous gap | Nokia, Nokia Shanghai Bell |
| R4-2004517 | Draft Response LS on CGI reading with autonomous gaps | Nokia, Nokia Shanghai Bell |
| R4-2004783 | Further discussion on interruption requirements for autonomous gaps for CGI reading | Qualcomm Incorporated |
| 6.15.1.4 | BWP switching on multiple CCs | |
| R4-2003202 | Discussion of RRM requirements for BWP switching on multiple CCs | Intel Corporation |
| R4-2003356 | Further consideration on BWP switch on mulitple CCs | vivo |
| R4-2003357 | Consideration on interruption period of BWP switching on multiple CCs | vivo |
| R4-2003379 | Further consideration on BWP switch on mulitple CCs | vivo |
| R4-2003380 | Consideration on interruption period of BWP switching on multiple CCs | vivo |
| R4-2003396 | RRM requirements for BWP switching on multiple CCs | Apple |
| R4-2003504 | Discussion on BWP switch on multiple CC | MediaTek inc. |
| R4-2003652 | Draft CR to TS 38.133: BWP switching on multiple CCs RRM requirements | Intel Corporation |
| R4-2003962 | Discussion on requirements for BWP switch delay on multiple CC | NEC |
| R4-2003980 | On RRM requirements for BWP switching on multiple CCs | OPPO |
| R4-2004244 | Discussion on partial overlap BWP switching on multiple CCs | Huawei, Hisilicon |
| R4-2004245 | Discussion on simultaneous BWP switching on multiple CCs | Huawei, Hisilicon |
| R4-2004406 | Further analysis of partially overlapped BWP triggering on multiple CCs | Ericsson |
| R4-2004425 | On Simultaneously Triggered BWP Switching on Multiple CCs | Ericsson |
| R4-2004518 | discussion on BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2004519 | CR on 36133 interruption requirements for BWP switching on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2004520 | CR on 38133 interruption requirements for BWP switching on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2004521 | CR on 38133 delay requirements for BWP switching on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2004784 | Further discussion on timeline for BWP switch for multiple cells | Qualcomm Incorporated |
| 6.15.1.5 | Inter-frequency measurement requirement without MG [NR_RRM_Enh-Core] | |
| R4-2003358 | Consideration on issues for inter-frequency measurement without gap | vivo |
| R4-2003381 | Consideration on issues for inter-frequency measurement without gap | vivo |
| R4-2003517 | RRM requirements on inter-frequency measurement without gap | CMCC |
| R4-2003518 | TP on introducing inter-frequency measurements without measurement gap | CMCC |
| R4-2003519 | LS on inter-frequency measurement requirement without MG | CMCC |
| R4-2003607 | Discussion on inter-frequency measurement requirement without gap | MediaTek inc. |
| R4-2003981 | On remaing issues for inter-frequency measurement without MG | OPPO |
| R4-2004301 | [Draft] LS on inter-frequency measurement requirement without MG | Huawei, Hisilicon |
| R4-2004302 | Discussion on inter-frequency measurement without gap | Huawei, Hisilicon |
| R4-2004785 | Further discussion on inter-frequency measurements without gaps | Qualcomm Incorporated |
| 6.15.1.6 | Mandatory MG patterns [NR_RRM_Enh-Core] | |
| R4-2003106 | Applicability of mandatory gaps for NR operating modes | Ericsson |
| R4-2003107 | LS on mandatory gap patterns for release 16 | Ericsson |
| R4-2003108 | Mandatory gap patterns in NR RRM enhancement | Ericsson |
| R4-2003477 | Further discussion on mandating gap patterns for Rel-16 NR | CMCC |
| R4-2003491 | Discussion on mandatory MG patterns | NTT DOCOMO, INC. |
| R4-2003606 | Discussion on new capability for NR-only measurement and mandatory MG patterns in Rel-16 | MediaTek inc. |
| R4-2003982 | Further discussion on mandatory measurement gap patterns and applicability | OPPO |
| R4-2004111 | LS on mandatory of measurement gap patterns | ZTE |
| R4-2004112 | Further discussion on mandatary of measurement gap patterns | ZTE |
| R4-2004303 | Discussion on mandatory gap pattern in R-16 | Huawei, Hisilicon |
| R4-2004304 | LS on mandatory gap patterns in R16 | Huawei, Hisilicon |
| R4-2004459 | Discussion on Mandatory GPs for NR Rel-16 | Nokia, Nokia Shanghai Bell |
| R4-2004789 | Further discussion on mandatory measurement gaps | Qualcomm Incorporated |
| 6.15.1.7 | UE-specific CBW change [NR_RRM_Enh-Core] | |
| R4-2003197 | Draft CR to TS 38.133: RRM requirement for UE-specific CBW change | Intel Corporation |
| R4-2003649 | Delay requirement for UE-specific channel bandwidth change | MediaTek inc. |
| R4-2003650 | RRM requirement for UE-specific CBW change | Intel Corporation |
| R4-2003651 | Draft CR to TS 38.133: RRM requirement for interruption due to UE-specific CBW change | Intel Corporation |
| R4-2003963 | Discussion on requirements for UE-specific CBW change | NEC |
| R4-2004373 | Discussion on RRM requirements for UE-specific CBW switching | Huawei, HiSilicon |
| R4-2004407 | UE specific channel BW change in FR1 and FR2 | Ericsson |
| 6.15.1.8 | Spatial relation switch for uplink [NR_RRM_Enh-Core] | |
| R4-2003198 | Draft CR to TS 38.133: UL spatial relation info switch RRM requirements | Intel Corporation |
| R4-2003205 | Discussion on requirements for spatial relation info switch | Intel Corporation |
| R4-2003397 | Requirements for Uplink Spatial Relation Info Switching | Apple |
| R4-2003492 | Discussion on spatial relation switch for uplink | NTT DOCOMO, INC. |
| R4-2003505 | Discussion on active spatial relation switch | MediaTek inc. |
| R4-2004305 | Discussion on spatial relation switch for uplink channels and SRS | Huawei, Hisilicon |
| R4-2004424 | On Spatial Relation Switching Delay Requirements | Ericsson |
| R4-2004460 | Discussion on UL spatial relation switch | Nokia, Nokia Shanghai Bell, Globalstar |
| R4-2004787 | Further discussion on requirements for spatial relation switch | Qualcomm Incorporated |
| 6.16 | NR RRM requirements for CSI-RS based L3 measurement [NR_CSIRS_L3meas] | |
| R4-2003431 | Discussions on CSI-RS for NR mobility, definitions and capabilities | Qualcomm CDMA Technologies |
| R4-2004826 | Discussions on CSI-RS for NR mobility, definitions and capabilities | Qualcomm CDMA Technologies |
| 6.16.1 | RRM core requirements (38.133) [NR_CSIRS_L3meas-Core] | |
| R4-2003408 | On CSI-RS based L3 measurement | Apple |
| 6.16.1.1 | CSI-RS measurement bandwidth [NR_CSIRS_L3meas-Core] | |
| R4-2003257 | Further discussion on CSI-RS measurement configuration for RRM measurement requirement | CATT |
| R4-2003476 | Further discussion on CSI-RS measurement bandwidth | CMCC |
| R4-2003482 | Discussion on CSI-RS parameters for RRM core requirements | NTT DOCOMO, INC. |
| R4-2003643 | Simulation results for CSI-RS measurement BW | MediaTek inc. |
| R4-2003807 | Discussion on CSI-RS measurement bandwidth | Nokia, Nokia Shanghai Bell |
| R4-2004113 | Discussion on bandwidth for CSI-RS based RRM measurement requirements | ZTE |
| R4-2004331 | Further discussion on CSI-RS based L3 measurement requirements | Huawei, HiSilicon |
| 6.16.1.2 | CSI-RS based intra-frequency and inter-frequency measurements definition [NR_CSIRS_L3meas-Core] | |
| R4-2003204 | Discussion about CSI-RS L3 measurement bandwidth and definition | Intel Corporation |
| R4-2003258 | Further discussion on definition of CSI-RS based intra-frequency and inter-frequency measurement | CATT |
| R4-2003259 | LS on CSI-RS based intra-frequency and inter-frequency Measurement definition | CATT |
| R4-2003475 | Further discussion on the definition of CSI-RS based intra-frequency measurements | CMCC |
| R4-2003483 | Definition of intra-frequency measurement for CSI-RS based L3 measurement | NTT DOCOMO, INC. |
| R4-2003644 | Definition of Intra and inter frequency for CSI-RS RRM | MediaTek inc. |
| R4-2003808 | CSI-RS based intra-f and inter-f measurement definition | Nokia, Nokia Shanghai Bell |
| R4-2003850 | Discussion on definition of CSI-RS based intra-frequency measurement | vivo |
| R4-2003964 | Definition of Intra and Inter-frequency CSI-RS based L3 measurements | NEC |
| R4-2003983 | On definition of CSI-RS based intra-frequency and inter-frequency measurements | OPPO |
| R4-2004115 | Further discussion on definition of CSI-RS based RRM measurements | ZTE |
| R4-2004290 | Definition for the CSI-RS based intra-frequency and inter-frequency measurement | Huawei, Hisilicon |
| R4-2004291 | [DRAFT] Reply LS on clarification about CSI-RS measurement | Huawei, Hisilicon |
| 6.16.1.3 | Measurement capability | |
| R4-2003203 | Discussion about CSI-RS L3 measurement capability and requirements | Intel Corporation |
| R4-2003260 | Further discussion on CSI-RS based UE measurement capabilities | CATT |
| R4-2003645 | Discussion on measurement capability for CSI-RS RRM | MediaTek inc. |
| R4-2003856 | Discussion on CSI-RS measurement capability | CMCC |
| R4-2003984 | On Measurement capability for CSI-RS L3 measurement | OPPO |
| R4-2004114 | Further discussion on UE measurement capability of CSI-RS based RRM measurements | ZTE |
| R4-2004374 | On CSI-RS measurement capability | Huawei, HiSilicon |
| 6.16.1.4 | Intra-frequency and inter-frequency measurement requirements [NR_CSIRS_L3meas-Core] | |
| R4-2003226 | Discussion on CSI-RS L3 measurement requirement | LG Electronics Inc. |
| R4-2003261 | Discussion on CSI-RS based measurement requirements | CATT |
| R4-2003484 | Discussion on measurement requirements for CSI-RS based L3 measurement | NTT DOCOMO, INC. |
| R4-2003646 | Cell identification requirements for CSI-RS RRM | MediaTek inc. |
| R4-2003809 | Applicability of CSI-RS based measurement requirements | Nokia, Nokia Shanghai Bell |
| R4-2003985 | On measurement requirement for CSI-RS based L3 measurements | OPPO |
| R4-2004292 | Discussion on CSI-RS based L3 measurement requirements | Huawei, Hisilicon |
| 6.16.1.5 | Others | |
| R4-2003262 | Discussion on the synchronization assumption for CSI-RS based measurement | CATT |
| R4-2003647 | Discussion on pre-emption on CSI-RS for L3 measurement | MediaTek inc. |
| R4-2003648 | Draft LS on pre-emption on CSI-RS for L3 measurement | MediaTek inc. |
| R4-2004375 | On synchronization assumption for CSI-RS measurement requirements | Huawei, HiSilicon |
| 6.17.1 | RRM core requirements (38.133) [NR_HST-Core] | |
| R4-2003263 | Further discussion on RRM requirements in NR HST scenarios | CATT |
| R4-2003430 | On NR HST RRM Requirements | Qualcomm, Inc. |
| R4-2003480 | Further discussion on RRM for NR high speed scenario | CMCC |
| R4-2003851 | Discussion on RLM and beam management requirement in NR HST | vivo |
| R4-2003857 | Discussion on SS-SINR measurement for NR HST | CMCC |
| 6.17.1.1 | Cell re-selection [NR_HST-Core] | |
| R4-2003098 | Requirements for idle mode mobility in high speed NR | Ericsson |
| R4-2003099 | Requirements for idle mode mobility in high speed NR | Ericsson |
| R4-2003264 | Draft CR on cell re-selection requirements for NR HST | CATT |
| R4-2003471 | Draft CR on cell re-selection requirements for Rel-16 NR HST for 38.133 | CMCC |
| R4-2004293 | Discussion on the RRM requirements in NR HST | Huawei, Hisilicon |
| R4-2004294 | Draft CR on cell reselection in NR HST | Huawei, Hisilicon |
| R4-2004452 | NR HST and Cell Reselection | Nokia, Nokia Shanghai Bell |
| R4-2004453 | TP for NR HST and Cell Reselection | Nokia, Nokia Shanghai Bell |
| 6.17.1.2 | Cell identification delay [NR_HST-Core] | |
| R4-2003100 | Requirements for RRC connected mode mobility in high speed NR | Ericsson |
| R4-2003101 | Requirements for RRC connected mode mobility in high speed NR | Ericsson |
| R4-2003265 | Draft CR on cell identification requirements for NR HST | CATT |
| R4-2003469 | Cell identification delay requirements for DRX case in HST scenario | NTT DOCOMO, INC. |
| R4-2003472 | Draft CR on cell identification requirements in connected mode for Rel-16 NR HST for 38.133 | CMCC |
| R4-2003852 | Discussion on intra-frequency requirements for connected mode UE in NR HST | vivo |
| R4-2004295 | Draft CR on cell identification in connected mode for NR HST | Huawei, Hisilicon |
| R4-2004383 | Discussions on measurement requirements for Rel-16 high speed train | Nokia, Nokia Shanghai Bell |
| R4-2004450 | NR HST and Connected mode RRM requirements | Nokia, Nokia Shanghai Bell |
| R4-2004451 | TP for HST RRM connected mode requirements | Nokia, Nokia Shanghai Bell |
| 6.17.1.3 | RLM [NR_HST-Core] | |
| R4-2004027 | RLM for NR HST | Ericsson |
| R4-2004454 | NR HST and RLM | Nokia, Nokia Shanghai Bell |
| R4-2004455 | TP for NR HST and RLM | Nokia, Nokia Shanghai Bell |
| 6.17.1.4 | Beam management [NR_HST-Core] | |
| R4-2004028 | BM for NR HST | Ericsson |
| R4-2004456 | Beam Management in HST | Nokia, Nokia Shanghai Bell |
| R4-2004457 | TP for Beam Management in HST | Nokia, Nokia Shanghai Bell |
| R4-2004458 | LS on SMTC periodicity for NR HST | Nokia, Nokia Shanghai Bell |
| 6.17.1.5 | Inter-RAT measurement | |
| R4-2003102 | Requirements for interRAT mobility in high speed | Ericsson |
| R4-2003473 | Draft CR on NR-EUTRAN inter-RAT measurement requirements for Rel-16 NR HST for 38.133 | CMCC |
| R4-2003474 | Draft CR on EUTRAN-NR inter-RAT measurement requirements for Rel-16 NR HST for 36.133 | CMCC |
| R4-2003481 | Further discussion on inter-RAT measurement requirements for NR HST | CMCC |
| R4-2003853 | Discussion on inter-RAT measurment requirements in NR HST | vivo |
| R4-2004296 | Draft CR on inter-RAT cell reselection in idle mode for NR HST in TS 36.133 | Huawei, Hisilicon |
| R4-2004297 | Draft CR on inter-RAT measurement for NR HST in TS 36.133 | Huawei, Hisilicon |
| 6.17.2.1 | UE demodulation and CSI requirements (38.101-4) [NR_HST-Perf] | |
| R4-2003191 | Views on NR UE demodulation requirements for HST | Intel Corporation |
| R4-2003478 | Further discussion on UE demodulation for NR HST | CMCC |
| R4-2003741 | Discussion on general issues for NR UE HST performance requirements | Huawei, HiSilicon |
| R4-2004006 | Views on release independent and applicability | NTT DOCOMO, INC. |
| R4-2004031 | Discussion on release independent requirements for NR HST | Ericsson |
| R4-2004476 | Views on Tests for High Speed Train Scenarios | Qualcomm Incorporated |
| 6.17.2.1.1 | Scenarios and transmission schemes [NR_HST-Perf] | |
| R4-2003187 | Views on NR UE demodulation requirements for different transmission schemes in HST-SFN scenario | Intel Corporation |
| R4-2003710 | Further discussion on transmission schemes for NR Rel-16 HST | Huawei, HiSilicon |
| R4-2003749 | Further discussion on transmission schemes for NR Rel-16 HST | Huawei, HiSilicon |
| R4-2003854 | Discussion on transmission scheme in NR HST | vivo |
| R4-2004029 | Transmission scheme in NR PDSCH demodulation requirements for HST | Ericsson |
| R4-2004913 | View on remain issues for Rel-16 NR UE HST | Samsung |
| 6.17.2.1.2 | Requirements for HST-SFN [NR_HST-Perf] | |
| R4-2003188 | Views on NR UE demodulation requirements for HST-SFN scenario | Intel Corporation |
| R4-2003711 | Discussion and simulation results on NR UE HST performance requirements for SFN | Huawei, HiSilicon |
| R4-2003750 | Discussion on NR UE HST performance requirements for SFN | Huawei, HiSilicon |
| R4-2004004 | Views on HST-SFN | NTT DOCOMO, INC. |
| R4-2004914 | Simulation results for UE demodulation requirements under HST SFN | Samsung |
| 6.17.2.1.3 | Requirements for HST single tap [NR_HST-Perf] | |
| R4-2003189 | Views on NR UE demodulation requirements for HST single tap scenario | Intel Corporation |
| R4-2003712 | Discussion and simulation results on NR UE HST performance requirements for single-tap | Huawei, HiSilicon |
| R4-2003751 | Discussion on NR UE HST performance requirements for single-tap | Huawei, HiSilicon |
| R4-2003830 | Simulation results for NR UE HST Single tap | Ericsson |
| R4-2004005 | Views on HST single-tap | NTT DOCOMO, INC. |
| R4-2004030 | Discussion on PDSCH demodulation performance with HST single tap | Ericsson |
| R4-2004915 | Simulation results for UE demodulation requirements under HST single tap | Samsung |
| 6.17.2.1.4 | Requirements for multi-path fading channels [NR_HST-Perf] | |
| R4-2003190 | Views on NR UE demodulation requirements for HST multi-path fading channel scenario | Intel Corporation |
| R4-2003713 | Discussion and simulation results on NR UE HST performance requirements for multi-path fading channel | Huawei, HiSilicon |
| R4-2003752 | Discussion on NR UE HST performance requirements for multi-path fading channel | Huawei, HiSilicon |
| R4-2003831 | Simulation results for HST Multipath fading channels | Ericsson |
| R4-2004003 | Views on multi-path fading | NTT DOCOMO, INC. |
| R4-2004916 | Simulation results for UE demodulation requirements under fading channel with high Doppler value | Samsung |
| R4-2004917 | Simulation results for UE demoudaltion requirements for TDD with specical slot | Samsung |
| 6.17.2.2 | BS demodulation requirements (38.104) [NR_HST-Perf] | |
| R4-2003270 | Summary of ideal and impairment results for NR HST demodulation requirements | CATT |
| R4-2003305 | Discussion on organization of NR HST requirements sections in specifications | CATT |
| R4-2003306 | Discussion on high speed support declaration for NR HST | CATT |
| R4-2003444 | Discussion on HST specification structure, declarations and applicability | Ericsson |
| R4-2003446 | Remain issues for HST BS demodulation | Ericsson |
| R4-2003479 | Discussion on BS demodulation for NR HST | CMCC |
| R4-2003958 | Further discussion on NR HST BS demodulation requirements | ZTE Wistron Telecom AB |
| R4-2004910 | View on remain issues for NR HST BS requirement | Samsung |
| 6.17.2.2.1 | PUSCH requirements [NR_HST-Perf] | |
| R4-2003309 | Discussion on antenna configuration for NR HST PUSCH tunnel scenario | CATT |
| R4-2003449 | Introducting of conformance tests for 350km/h HST | Ericsson |
| R4-2003628 | Views on NR PUSCH for high speed | NTT DOCOMO, INC. |
| R4-2003714 | Discussion on NR BS HST performance requirements | Huawei, HiSilicon |
| R4-2003890 | On NR Rel-16 HST BS demodulation PUSCH requirements | Nokia, Nokia Shanghai Bell |
| R4-2003891 | NR Rel-16 HST BS demodulation further PUSCH requirements simulation results | Nokia, Nokia Shanghai Bell |
| R4-2003892 | draftCR for 38.104: HST PUSCH demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2003893 | draftCR for 38.104: HST PUSCH demodulation FRC and channel model annexes | Nokia, Nokia Shanghai Bell |
| R4-2004794 | Simulation results for NR HST PUSCH | Intel Corporation |
| R4-2004911 | Discussion and simulation results for NR HST PUSCH | Samsung |
| 6.17.2.2.2 | PRACH requirements [NR_HST-Perf] | |
| R4-2003308 | Discussion on fading channel for NR HST PRACH | CATT |
| R4-2003629 | Views on NR PRACH for high speed | NTT DOCOMO, INC. |
| R4-2003688 | Draft CR on 38.104 Introduction of PRACH demodulation requirements for NR HST | Huawei, HiSilicon |
| R4-2003689 | Draft CR on 38.141-1 Introduction of PRACH demodulation requirements for NR HST | Huawei, HiSilicon |
| R4-2003690 | Draft CR on 38.141-2 Introduction of PRACH demodulation requirements for NR HST | Huawei, HiSilicon |
| R4-2003691 | Discussion on open issues for NR HST PRACH | Huawei, HiSilicon |
| R4-2003894 | On NR Rel-16 HST BS demodulation PRACH requirements | Nokia, Nokia Shanghai Bell |
| R4-2004795 | Simulation results for NR HST PRACH | Intel Corporation |
| 6.17.2.2.3 | UL timing adjustment requirements [NR_HST-Perf] | |
| R4-2003268 | Discussion on test parameters for NR PUSCH UL timing | CATT |
| R4-2003269 | Simulation results for NR PUSCH UL timing | CATT |
| R4-2003271 | Draft CR for TS 38.141-2: introduction of NR PUSCH UL timing adjustment | CATT |
| R4-2003272 | Draft CR for TS 38.141-2: appendix for NR PUSCH UL timing adjustment | CATT |
| R4-2003307 | Discussion on relationship between TDD and FDD requirements for NR HST PUSCH UL TA | CATT |
| R4-2003448 | NR PUSCH UL timing adjustment simulation results for 95% of maximum throughput test metric | Ericsson |
| R4-2003630 | Views on NR PUSCH for UL timing adjustment | NTT DOCOMO, INC. |
| R4-2003715 | Simulation results on NR HST PUSCH performance requirements | Huawei, HiSilicon |
| R4-2003895 | On NR Rel-16 HST BS demodulation UL timing adjustment requirements | Nokia, Nokia Shanghai Bell |
| R4-2003957 | draftCR for 38.104: Radiated performance requirements for UL timing adjustment | ZTE Wistron Telecom AB |
| R4-2004908 | draft CR on UL timing adjustment conducted performance requirement for TS 38.141-1 | Samsung |
| R4-2004909 | draft CR on FRC and moving progagation condition for UL timing adjustment for TS 38.141-1 | Samsung |
| R4-2004912 | Discussion and simulation results for NR HST UL timing requirement | Samsung |
| 6.18.1 | UE demodulation and CSI requirements (38.101-4) [NR_perf_enh-Perf] | |
| R4-2003719 | Discussion on release independent for NR Rel-16 enhanced UE demodulation requirements | Huawei, HiSilicon |
| 6.18.1.1 | NR CA PDSCH requirements [NR_perf_enh-Perf] | |
| R4-2003185 | Discussion on NR CA UE demodulation requirements | Intel Corporation |
| R4-2003520 | Test applicability rule for NR CA PDSCH normal demodulation | CMCC |
| R4-2003717 | Discussion on HARQ timing for NR UE normal CA performance requirements | Huawei, HiSilicon |
| R4-2003718 | Discussion on NR Rel-16 UE CA normal demodulation requirements | Huawei, HiSilicon |
| R4-2003721 | draftCR: test structure for NR FR1 CA normal demodulation requirements for 4Rx | Huawei, HiSilicon |
| R4-2004008 | Views on on PDSCH CA normal demodulation requirements | NTT DOCOMO, INC. |
| R4-2004210 | Views on NR CA PDSCH Demodulation Performance Tests | Qualcomm Incorporated |
| R4-2004212 | Simulation Results for NR CA PDSCH Demodulation Performance Tests | Qualcomm Incorporated |
| R4-2004553 | Simulation results for Normal CA requirements | Intel Corporation |
| R4-2004554 | Summary of Normal CA simulation results (FR1 15 kHz FDD and TDD) | Intel Corporation |
| R4-2004555 | Summary of Normal CA simulation results (FR1 30 kHz TDD) | Intel Corporation |
| R4-2004556 | Summary of Normal CA simulation results (FR2) | Intel Corporation |
| R4-2004897 | On NR CA PDSCH normal demodulation requirements | China Telecom |
| R4-2004898 | Simulation results for NR CA PDSCH normal demodulation requirements | China Telecom |
| 6.18.1.2 | PMI reporting requirements with larger number of Tx ports [NR_perf_enh-Perf] | |
| R4-2003692 | Simulation results for PMI reporting test with larger Tx ports | Huawei, HiSilicon |
| R4-2003693 | Discussion on open issues for PMI test for Tx ports larger than 8 | Huawei, HiSilicon |
| R4-2003822 | Evaluation on test metrics for Type II codebook | Ericsson |
| R4-2003823 | Simulation results for SP Type I | Ericsson |
| R4-2003824 | Summary of simulation results of NR UE CSI PMI with 16, and 32Tx antennas | Ericsson |
| R4-2004427 | Parameters and simulation results on PMI reporting requirements with larger number of Tx ports | Qualcomm Incorporated |
| R4-2004899 | Simulation results for PMI reporting requirements | China Telecom |
| R4-2004921 | Simulation results for PMI reporting with type I codebook | Samsung |
| R4-2004922 | Discussion and simulation results for PMI requirement with NR Rel-15 type II codebook | Samsung |
| 6.18.1.4 | FR1 CA and EN-DC power imbalance requirements [NR_perf_enh-Perf] | |
| R4-2003186 | Discussion on FR1 CA and EN-DC power imbalance requirements | Intel Corporation |
| R4-2003521 | Discussion on FR1 CA power imbalance requirements | CMCC |
| R4-2003720 | Discussion on NR UE performance requirements for power imbalance | Huawei, HiSilicon |
| R4-2004009 | Views on power imbalance requirement | NTT DOCOMO, INC. |
| R4-2004792 | Views on Power Imbalance Tests | Qualcomm Incorporated |
| R4-2004900 | FR1 CA PDSCH demodulation requirement with power imbalance | China Telecom |
| 6.18.1.5 | NR CA CQI reporting requirements [NR_perf_enh-Perf] | |
| R4-2003694 | Discussion on reporting of Channel Quality Indicator (CQI) for CA | Huawei, HiSilicon |
| R4-2004813 | Views on CA CQI Reporting Tests | Qualcomm Incorporated |
| R4-2004901 | On NR CA CQI reporting requirements | China Telecom |
| 6.18.2.1 | 30% TP test point [NR_perf_enh-Perf] | |
| R4-2003273 | Discussion on organization of PUSCH requirements with 30% throughput test point in specifications | CATT |
| R4-2003274 | Simulation results for NR PUSCH with 30% throughput test point | CATT |
| R4-2003275 | Draft CR for TS 38.104: Introduce PUSCH performance requirements at 30% throughput test point | CATT |
| R4-2003276 | Draft CR for TS 38.141-1: Introduce PUSCH performance requirements at 30% throughput test point | CATT |
| R4-2003277 | Draft CR for TS 38.141-2: Introduce PUSCH performance requirements at 30% throughput test point | CATT |
| R4-2003445 | Discussion on Structure and applicability rule for 30% TP test point | Ericsson |
| R4-2003447 | Discussion on PUSCH demodulation requirements at 30% Thp | Ericsson |
| R4-2003545 | Summary of ideal and impairment results for NR PUSCH with 30% throughput test point | CATT |
| R4-2003627 | Remaining issues on PUSCH 30% TP test point | NTT DOCOMO, INC. |
| R4-2003700 | Disc on NR PUSCH 30percent TP perf capturing | Huawei, HiSilicon |
| R4-2003701 | Simulation results for NR Rel-16 BS performance requirements for 30% TP test point | Huawei, HiSilicon |
| R4-2003896 | On NR Rel-16 performance requirement enhancement BS demodulation 30% TP test point | Nokia, Nokia Shanghai Bell |
| R4-2003897 | NR Rel-16 performance requirement enhancement BS demodulation simulation results | Nokia, Nokia Shanghai Bell |
| R4-2003954 | On Rel-16 demodulation requirements for 30% throughput testing points | ZTE Wistron Telecom AB |
| R4-2004902 | On channel bandwidth for 30% throughput PUSCH demodulation requirements | China Telecom |
| R4-2004903 | Simulation results for 30% throughput PUSCH demodulation requirements | China Telecom |
| R4-2004920 | Updated simulation results for Rel-16 performance enhancement | Samsung |
| 6.18.2.2 | Additional FR2 requirements | |
| R4-2003898 | draftCR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| R4-2003899 | draftCR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM | Nokia, Nokia Shanghai Bell |
| 6.19.1 | General [OTA_BS_testing-Perf] | |
| R4-2003997 | Draft TR 37.941 v0.1.0 | Huawei |
| R4-2003998 | TP to TR 37.941: general sections | Huawei |
| R4-2004037 | TP to TR 37.941: Improvement to increase readability in Clause 6 | Ericsson, Rohde&Schwarz |
| R4-2004641 | TP to TR 37.941: cleanup | Huawei |
| 6.19.2 | OTA calibration and test method procedures [OTA_BS_testing-Perf] | |
| R4-2004038 | TP to TR 37.941: Addition of technical background for co-location requirements in subclause 6.4 | Ericsson |
| R4-2004039 | TP to TR 37.941: Correction to reverberation description | Ericsson |
| R4-2004099 | TP to TR 37.941: Improvement of text in subclause 6.3.2 | Ericsson LM |
| R4-2004392 | Ambiguity on two orthogonal polarizations measurements | ROHDE & SCHWARZ |
| R4-2004393 | Justification for additional Tx test cases for PWS | ROHDE & SCHWARZ |
| R4-2004394 | TP to TR 37.941 to introduce additional Tx test cases for PWS | ROHDE & SCHWARZ |
| 6.19.3 | Coordinate system [OTA_BS_testing-Perf] | |
| R4-2003999 | TP to TR 37.941: coordinate system | Huawei |
| R4-2004042 | TP to the TR 37.941: Coordinate system | Ericsson, Rohde&Schwarz |
| R4-2004525 | Discussions on the spherical coordinate system | Nokia, Nokia Shanghai Bell |
| R4-2004793 | TP to TR 37.941: Coordinate system | Nokia, Nokia Shanghai Bell |
| 6.19.4 | Conformance testing aspects [OTA_BS_testing-Perf] | |
| R4-2004000 | TP to TR 37.941: conformance testing framework | Huawei |
| R4-2004040 | TP to TR 37.941: MU budget format for RC | Ericsson |
| R4-2004041 | TP to the TR 37.941: Conformance Framework | Ericsson |
| 6.19.5 | MU / TT values: derivation and tables [OTA_BS_testing-Perf] | |
| R4-2004527 | OTA BS testing Tx FR1 MU calculation tables | Huawei |
| R4-2004528 | TP to TR 37.941 -Tx MU value derivation sub-clause 9 update (FR1) | Huawei |
| R4-2004529 | OTA BS testing Tx FR2 MU calculation tables | Huawei |
| R4-2004530 | TP to TR 37.941 -Tx MU value derivation sub-clause 9 update (FR2) | Huawei |
| R4-2004531 | TP to TR 37.941 -RX MU value derivation sub-clause 10 update (FR1) | Huawei |
| R4-2004532 | OTA BS testing Rx FR2 MU calculation tables | Huawei |
| R4-2004533 | TP to TR 37.941 -RX MU value derivation sub-clause 10 update (FR2) | Huawei |
| R4-2004534 | OTA BS testing RX FR1 MU calculation tables - correction | Huawei |
| R4-2004535 | TP to TR 37.941 Tx TRP emissions MU value derivation sub-clause 11 updates (FR1) | Huawei |
| R4-2004536 | TP to TR 37.941: Tx TRP emissions MU value derivation sub-clause 11 updates (FR2) | Huawei |
| R4-2004537 | Spurious emissions MU value derivation sub-clause 12 update (FR1) | Huawei |
| R4-2004538 | TP to TR 37.941 - Spurious emissions MU value derivation sub-clause 12 update (FR2) | Huawei |
| 6.19.6 | Annexes [OTA_BS_testing-Perf] | |
| R4-2004526 | TP to TR 37.941 : Test uncertainty annexes - update | Huawei |
| 6.19.7 | Others [OTA_BS_testing-Perf] | |
| R4-2004642 | TP to TR 37.941: co-location measurements description | Huawei |
| R4-2004643 | TP to TR 37.941: reverberation chamber description correction | Huawei |
| 6.20 | 2-step RACH for NR | |
| R4-2004117 | Work plan for 2-step RACH | ZTE |
| 6.20.1 | RRM core requirements (38.133) [NR_2step_RACH-Core] | |
| R4-2003393 | On RRM core requirements for 2-step RACH | Nokia, Nokia Shanghai Bell |
| R4-2003394 | Draft CR to TS 38.133: introducing 2-step RACH core requirements | Nokia, Nokia Shanghai Bell |
| R4-2003965 | Discussion on RRM Requirements for 2-step RACH | NEC |
| R4-2003966 | draft CR to TS 381.33 v16.3.0: on UE behaviour for contention based 2-step RACH | NEC |
| R4-2004022 | RRM requirements for 2-step RACH procedures | Ericsson |
| R4-2004116 | Further discussion on RRM requirements for 2-step RACH | ZTE |
| R4-2004118 | draft CR to 38.133 on 2-step RACH RRM requirements | ZTE |
| R4-2004413 | Impact of 2-step RACH on exisitng RRM requirements | Ericsson |
| R4-2004808 | RRM core requirements for 2-step RACH | Qualcomm |
| 6.20.2 | BS Demodulation requirements (38.104/38.141-1/38.141-2) [NR_2step_RACH-Perf] | |
| R4-2003392 | On 2-step RACH BS demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2003709 | Discussion on NR 2-step RACH BS performance requirements | Huawei, HiSilicon |
| R4-2003748 | Discussion on performance requirements for 2-step RACH | Huawei, HiSilicon |
| R4-2003841 | 2 step RACH demodulation requirements | Ericsson |
| R4-2003950 | BS demodulation performance requirements for 2-step RACH | ZTE Wistron Telecom AB |
| R4-2004796 | Views on NR BS demodulation requirements for 2-Step RACH | Intel Corporation |
| R4-2004918 | View on BS demodulation requirement for NR 2-step RACH | Samsung |
| 7 | UE feature list | |
| R4-2003470 | RAN4 UE features list for Rel-16 | NTT DOCOMO, INC. |
| R4-2003662 | Consideration on high power UE fall back enhancement | Xiaomi |
| R4-2004701 | Views on NR UE feature list for FR1 | Apple Inc. |
| R4-2004702 | Views on NR UE feature list for FR2 | Apple Inc. |
| 8 | Rel-16 spectrum related Work Items for NR | |
| R4-2004957 | Proposal of US C-band | Verizon UK Ltd |
| 8.1.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_intra-Core /Perf] | |
| R4-2004568 | Revised WID NR Intra-band Rel-16 | Ericsson |
| R4-2004576 | TR 38.716-01-01 v0.10.0 Rel-16 NR Intra-band | Ericsson |
| R4-2004579 | TP for TR 38.716-01-01 for updated scope from RAN #87 | Ericsson |
| R4-2004583 | draft CR introduction completed band combinations 38.716-01-01 -> 38.101-1 | Ericsson |
| R4-2004584 | draft CR introduction completed band combinations 38.716-01-01 -> 38.101-2 | Ericsson |
| 8.1.2 | UE RF for FR1 [NR_CA_R16_intra-Core] | |
| R4-2003159 | TP for TR 38.716-01-01: CA_n41B_UL_n41B | Samsung, KDDI |
| R4-2003160 | TP for TR 38.716-01-01: CA_n77(2A)_UL_n77(2A) | Samsung, KDDI |
| R4-2003161 | TP for TR 38.716-01-01: CA_n78(2A)_UL_n78(2A) | Samsung, KDDI |
| R4-2003421 | TP for TR 38.716-01-01 for CA_n48(3A) and CA_n48(4A) | Charter Communications, Inc |
| R4-2003947 | Updated TP for TR 38.716-01-01: to add BCS1 for CA_n71B | Huawei, HiSilicon, CITC |
| R4-2004997 | Considerations for n48 CA BW combinations | Dish Network |
| 8.1.3 | UE RF for FR2 [NR_CA_R16_intra-Core] | |
| R4-2003530 | Draft CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications | MediaTek Inc. |
| R4-2003595 | Drat CR to TS 38.101-2 on corrections to NR CA band for FR2 (Rel-16) | ZTE Corporation |
| R4-2003596 | Draft CR to TS 38.101-2 on intra-band non-contiguous CA ordering (Rel-16) | ZTE Corporation |
| 8.2.1 | Rapporteur Input (WID/TR/CR) [NR_CADC_R16_2BDL_xBUL-Core/Perf] | |
| R4-2003798 | Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) | ZTE Corporation |
| R4-2003799 | Draft CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-1 | ZTE Corporation |
| R4-2003800 | Draft CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-3 | ZTE Corporation |
| R4-2003951 | TR 38.716-02-00 v100 | ZTE Wistron Telecom AB |
| R4-2004958 | Draft CR to add simultaneous RX/TX capability for inter-band CA | CMCC, ZTE |
| 8.2.2 | NR inter band CA without any FR2 band(s) [NR_CADC_R16_2BDL_xBUL-Core] | |
| R4-2003168 | Draft CR for 38.101-1 to introduce new UL CA configuration for inter band NR CA for 2BDL with xBUL | Samsung, KDDI |
| R4-2003170 | Draft CR for 38.101-3 to introduce new inter band NR CA and DC for 2BDL with xBUL between FR1 and FR2 | Samsung, KT, KDDI |
| R4-2003586 | TP to TR 38.716-02-00 CA_n78A-n92A | Huawei, HiSilicon |
| R4-2003789 | Draft CR to TS38.101-1[R16]_Adding the missing NR CA combs in the REFSEN expection tables | ZTE Corporation |
| R4-2003945 | Updated TP for TR 38.716-02-00: to add UL configuration for CA_n41A-n78A | Huawei, HiSilicon,Etisalat |
| R4-2004067 | TP for 38.716-02-00 for CA_n40A-n78(2A) | Huawei, HiSilicon |
| R4-2004068 | TP to TR 38.716-02-00 for CA_n7-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004595 | TP for TR 38.716-02-00 to include CA_n41A-n71A | Ericsson, T-Mobile |
| R4-2004596 | TP for TR 38.716-02-00 to include A_n25A-n71A | Ericsson, T-Mobile |
| R4-2004597 | TP for TR 38.716-02-00 to include CA_n41A-n66A | Ericsson, T-Mobile |
| R4-2004614 | TP for TR 38.716-02-00 to include CA_n1A-n40A | Ericsson |
| R4-2004615 | TP for TR 38.716-02-00 to include CA_n28A-n40A | Ericsson |
| R4-2004932 | Draft CR for TS 38.101-1: UL harmonic MSD and OOBB exception | MediaTek Inc. |
| R4-2004991 | TP for TR38.716-02-00: Requirements UL CA_n66A-n71A and corrections to UL CA_n66A-71A and UL CA_n70-n71A UE Co-existence spurious emissions | Dish Network |
| R4-2004996 | Corrections to UL CA_n66-n71 and UL CA_n70-n71 UE Co-existence spurious emissions | Dish Network |
| 8.2.3 | NR inter band CA with at least one FR2 band [NR_CADC_R16_2BDL_xBUL-Core] | |
| R4-2003597 | Drat CR to TS 38.101-3 on corrections to inter-band CA configurations between FR1 and FR2 (Rel-16) | ZTE Corporation |
| R4-2004606 | TP for TR 38.716-02-00 to include CA_n78-n258 | Ericsson, Telstra |
| 8.3.1 | Rapporteur Input (WID/TR/CR) m[DC_R16_1BLTE_1BNR_2DL2UL-Core/Perf] | |
| R4-2003778 | TR 37.716-11-11 v.1.2.0 Rel.16 1 LTE band + 1 NR band EN-DC | CHTTL |
| R4-2003821 | draft big CR on introduction of completed EN-DC of 1 band LTE and 1 band NR | CHTTL |
| 8.3.2 | EN-DC without FR2 band [DC_R16_1BLTE_1BNR_2DL2UL-Core] | |
| R4-2003119 | TP for TR 37.716-11-11: DC_41_n3 | Samsung, KDDI |
| R4-2003120 | TP for TR 37.716-11-11: DC_41_n28 | Samsung, KDDI |
| R4-2003121 | TP for TR 37.716-11-11: DC_41_n78-n78 | Samsung, KDDI |
| R4-2003169 | Draft CR for 38.101-3 to introduce new BCS of intra-band EN-DC | Samsung, KDDI |
| R4-2003441 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_42_n77 | SoftBank Corp. |
| R4-2003459 | TP for TR 37.716-11-11: DC_42_n28 | SoftBank Corp. |
| R4-2003917 | TP for TR 37.716-11-11: DC_1A_n20A | Huawei, HiSilicon |
| R4-2003918 | TP for TR 37.716-11-11: DC_8A_n20A | Huawei, HiSilicon |
| R4-2003919 | Updated TP for TR 37.716-11-11: DC_3A_n8A | Huawei, HiSilicon |
| R4-2003920 | TP for TR 37.716-11-11: DC_1A_n71A\DC_1A_n71B | Huawei, HiSilicon, CITC |
| R4-2003921 | TP for TR 37.716-11-11: DC_3A_n71A\DC_3A_n71B | Huawei, HiSilicon, CITC |
| R4-2003922 | DraftCR for 38.101-3 to add configuration DC_28A_n78(2A) | Huawei, HiSilicon,Etisalat |
| R4-2003923 | DraftCR for 38.101-3 to add configuration DC_20A_n78(2A) | Huawei, HiSilicon,Etisalat |
| R4-2003924 | DraftCR for 38.101-3 to add configuration DC_41D_n78A | Huawei, HiSilicon,Etisalat |
| R4-2003925 | TP for TR 37.716-11-11: DC_(n)38AA | Huawei, HiSilicon |
| R4-2003926 | DraftCR for 38.101-3 to add BCS2 for DC_(n)41DA | Huawei, HiSilicon,Etisalat |
| R4-2004064 | Correction to EN-DC coexistence requirements | Rohde & Schwarz |
| R4-2004219 | TP for 37.716-11-11 to introduce DC_7_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004385 | CR for EN-DC_1A_n40A MSD for cross band noise | Qualcomm Incorporated |
| R4-2004398 | Draft CR for TS 38.101-3: Introduction of DC_39A_n79C and DC_41A_n79C | Qualcomm Incorporated |
| R4-2004494 | TP for 37.716-11-11: DC_66A_n7(2A) | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004495 | Draft CR to 38.101-3: DC_7A-7A_n78(2A) and DC_66A-66A_n78(2A) | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004592 | TP for TR 37.716-11-11 to include DC_12_n41 | Ericsson, T-Mobile |
| R4-2004607 | TP for TR 37.716-11-11 to include DC_3A_n8A | Ericsson |
| R4-2004608 | TP for TR 37.716-11-11 to include DC_7A_n8A | Ericsson |
| R4-2004609 | TP for TR 37.716-11-11 to include DC_28A_n40A | Ericsson |
| R4-2004627 | TP for TR 37.716-11-11 to include DC_12_n71 | Ericsson, US Cellular |
| R4-2004864 | Correction TP for TR 37.716-11-11: DC_B28_n50, DC_11_n3, DC_28_n5 | MediaTek Inc. |
| R4-2004890 | TP for TR37.716-11-11: UE MSD requirements for DC_(n)5AA | MediaTek Inc. |
| R4-2004891 | TP for TR37.716-11-11: UE MSD requirements for DC_(n)12AA | MediaTek Inc. |
| R4-2004935 | Draft CR for TS 38.101-3: Adding missing MSD due to UL harmonic for DC_28_n50 | MediaTek Inc. |
| R4-2004953 | TP for TR 37.716-11-11: DC_66_n5A | Verizon UK Ltd |
| 8.3.3 | EN-DC with FR2 band [DC_R16_1BLTE_1BNR_2DL2UL-Core] | |
| R4-2003835 | TP for TR 37.716-11-11 for 39A_n257 | Qualcomm Incorporated |
| R4-2004954 | TP for TR 37.716-11.11: DC_5A_n261A | Verizon UK Ltd |
| R4-2004955 | TP for TR 37.716-11-11: DC_66A_n260 | Verizon UK Ltd |
| 8.4.1 | Rapporteur Input (WID/TR/CR) [DC_R16_2BLTE_1BNR_3DL2UL-Core/Perf] | |
| R4-2004501 | TR 37.716-21-11 v0.10.0 | Huawei, HiSilicon |
| R4-2004502 | Revised WID: Dual Connectivity (EN-DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) | Huawei, HiSilicon |
| R4-2004503 | Draft CR on introduction of completed EN-DC of 2 bands LTE and 1 band NR from RAN4#94bis-e into TS 38.101-3 | Huawei, HiSilicon |
| 8.4.2 | EN-DC without FR2 band [DC_R16_2BLTE_1BNR_3DL2UL-Core] | |
| R4-2003122 | TP for TR 37.716-21-11: DC_1-41_n3 | Samsung, KDDI |
| R4-2003123 | TP for TR 37.716-21-11: DC_1-41_n28 | Samsung, KDDI |
| R4-2003124 | TP for TR 37.716-21-11: DC_1-41_n77-n77 | Samsung, KDDI |
| R4-2003125 | TP for TR 37.716-21-11: DC_1-41_n78-n78 | Samsung, KDDI |
| R4-2003126 | TP for TR 37.716-21-11: DC_3-41_n28 | Samsung, KDDI |
| R4-2003127 | TP for TR 37.716-21-11: DC_3-41_n77-n77 | Samsung, KDDI |
| R4-2003128 | TP for TR 37.716-21-11: DC_3-41_n78-n78 | Samsung, KDDI |
| R4-2003129 | TP for TR 37.716-21-11: DC_11A-18A_n77A | Samsung, KDDI |
| R4-2003130 | TP for TR 37.716-21-11: DC_11A-18A_n78A | Samsung, KDDI |
| R4-2003131 | TP for TR 37.716-21-11: DC_18-41_n3 | Samsung, KDDI, LG Electronics Inc. |
| R4-2003132 | TP for TR 37.716-21-11: DC_18-41_n77 | Samsung, KDDI, LG Electronics Inc. |
| R4-2003133 | TP for TR 37.716-21-11: DC_18-41_n78 | Samsung, KDDI, LG Electronics Inc. |
| R4-2003167 | TP for TR 37.716-21-11: DC_2-48_n66 | Samsung, Verizon |
| R4-2003440 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_3-8_n77 | SoftBank Corp. |
| R4-2003451 | TP for TR 37.716-21-11: EN-DC_1-11_n3 | SoftBank Corp. |
| R4-2003454 | TP for TR 37.716-21-11: EN-DC_3-8_n28 | SoftBank Corp. |
| R4-2003457 | TP for TR 37.716-21-11: EN-DC_8-11_n3 | SoftBank Corp. |
| R4-2003488 | TP for TR 37.716-21-11: support of DC_3-3-7_n77, DC_3-7-7_n77, DC_3-3-7-7_n77 | CHTTL |
| R4-2003581 | TP to TR 37.716-21-11 DC_1A-20A_n41A | Huawei, HiSilicon |
| R4-2003582 | TP to TR 37.716-21-11 DC_3A-20A_n41A | Huawei, HiSilicon |
| R4-2003583 | TP to TR 37.716-21-11 DC_1A-3C_n41A | Huawei, HiSilicon |
| R4-2003927 | Updated TP for TR 37.716-21-11: add configuration DC_1A-(n)41DA | Huawei, HiSilicon,Etisalat |
| R4-2003928 | TP for TR 37.716-21-11: DC_1A-3A_n71A\DC_1A-3A_n71B | Huawei, HiSilicon, CITC |
| R4-2003929 | TP for TR 37.716-21-11: DC_7A-8A_n3A | Huawei, HiSilicon |
| R4-2003930 | TP for TR 37.716-21-11: DC_1A-(n)38AA | Huawei, HiSilicon |
| R4-2003931 | TP for TR 37.716-21-11: DC_20A-(n)38AA | Huawei, HiSilicon |
| R4-2003932 | TP for TR 37.716-21-11: DC_20A-(n)41AA\DC_20A-(n)41CA\DC_20A-(n)41DA | Huawei, HiSilicon,Etisalat |
| R4-2003933 | TP for TR 37.716-21-11: DC_(n)41AA-n78A\DC_(n)41CA-n78A\DC_(n)41DA-n78A | Huawei, HiSilicon,Etisalat |
| R4-2003934 | TP for TR 37.716-21-11: DC_1A-32A_n78A\DC_1A-32A_n78(2A) | Huawei, HiSilicon |
| R4-2003935 | TP for TR 37.716-21-11: DC_3A-32A_n78A\DC_3A-32A_n78(2A) | Huawei, HiSilicon |
| R4-2003936 | TP for TR 37.716-21-11: DC_20A-32A_n78A\DC_20A-32A_n78(2A) | Huawei, HiSilicon |
| R4-2003937 | DraftCR for 38.101-3 to add UL configuration DC_7C_n78A for DC_7C-28A_n78A,DC_3A-7C_n78A,DC_3C-7C_n78A and DC_3C_n78A for DC_3C-7A_n78A,DC_3C-7C_n78A | Huawei, HiSilicon |
| R4-2003938 | Updated TP for TR 37.716-31-11: to add UL configuration DC_7C_n78A for DC_1A-7C-28A_n78A | Huawei, HiSilicon |
| R4-2004220 | TP for 37.716-21-11 to introduce DC_1-7_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004221 | TP for 37.716-21-11 to introduce DC_3-7_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004222 | TP for 37.716-21-11 to introduce DC_7-28_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004400 | Draft CR to TS 38.101-3 on delta TIB and RIB for 2BLTE-1BNR (Rel-16) | ZTE Corporation |
| R4-2004496 | TP for TR 37.716-21-11: Additional band combinations for DC_2-66_n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004497 | TP for TR 37.716-21-11: Additional band combinations for DC_2-7_n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004498 | TP for TR 37.716-21-11: Additional band combinations for DC_7-66_n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004593 | draft Rel-16 CR to 38.101-3 to add DC_2-46_n41 and DC_46-66_n41 configurations | Ericsson, T-Mobile |
| R4-2004610 | TP for TR 37.716-21-11 to include DC_1A-3A_n40A | Ericsson |
| R4-2004611 | TP for TR 37.716-21-11 to include DC_1A-28A_n40A | Ericsson |
| R4-2004612 | TP for TR 37.716-21-11 to include DC_3A-28A_n40A | Ericsson |
| R4-2004628 | TP for TR 37 716-21-11 to include DC_12A-48A_n71A | Ericsson, US Cellular |
| R4-2004629 | TP for TR 37 716-21-11 to include DC_12A-66A_n71A | Ericsson, US Cellular |
| R4-2004636 | TP for TR 37.716-21-11: DC_25A-41D_n41A and DC_25A-25A-41D_n41A corrections | T-Mobile USA Inc. |
| R4-2005004 | TP to TR 37.716-21-11: Addition of 2A_(n)12AA | Nokia, US Cellular |
| R4-2005005 | TP to TR 37.716-21-11: Addition of 5A_(n)12AA | Nokia, US Cellular |
| R4-2005006 | TP to TR 37.716-21-11: Addition of 12A_(n)5AA | Nokia, US Cellular |
| R4-2005007 | TP to TR 37.716-21-11: Addition of 48A_(n)5AA | Nokia, US Cellular |
| R4-2005008 | TP to TR 37.716-21-11: Addition of DC_2A-12A_n71A | Nokia, US Cellular |
| R4-2005009 | TP to TR 37.716-21-11: Addition of DC_5A-12A_n71A | Nokia, US Cellular |
| 8.5.1 | Rapporteur Input (WID/TR/CR) [DC_R16_3BLTE_1BNR_4DL2UL-Core/Perf] | |
| R4-2004569 | Revised WID LTE 3DL and one NR band Rel-16 | Ericsson |
| R4-2004577 | TR 37.716-31-11 v0.10.0 Rel-16 DC combinations LTE 3DL and one NR band | Ericsson |
| R4-2004580 | TP for TR 37.716-31-11 for updated scope from RAN #87 | Ericsson |
| R4-2004585 | draft CR introduction completed band combinations 37.716-31-11 -> 38.101-3 | Ericsson |
| 8.5.2 | EN-DC without FR2 band [DC_R16_3BLTE_1BNR_4DL2UL-Core] | |
| R4-2003157 | TP for TR 37.716-31-11: DC_1-3-41_n77-n77 | Samsung, KDDI |
| R4-2003158 | TP for TR 37.716-31-11: DC_1-3-41_n78-n78 | Samsung, KDDI |
| R4-2003584 | TP to TR 37.716-31-11 DC_1A-3A-20A_n41A | Huawei, HiSilicon |
| R4-2004133 | Updated TP for TR 37.716-31-11: to add UL configuration DC_7C_n78A for DC_1A-7C-28A_n78A | Huawei, HiSilicon |
| R4-2004223 | TP for 37.716-31-11 to introduce DC_1-7-28_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004224 | TP for 37.716-31-11 to introduce DC_1-3-7_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004225 | TP for 37.716-31-11 to introduce DC_3-7-28_n40 | Nokia, Nokia Shanghai Bell |
| R4-2004594 | draft Rel-16 CR to 38.101-3 to add DC_2-46-66_n41 configurations | Ericsson, T-Mobile |
| R4-2004613 | TP for TR 37.716-31-11 to include DC_1A-3A-28A_n40A | Ericsson |
| R4-2004630 | TP for TR 37 716-31-11 to include DC_12A-48A-66A_n71A | Ericsson, US Cellular |
| R4-2004631 | TP for TR 37 716-31-11 to include DC_2A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2004632 | TP for TR 37 716-31-11 to include DC_2A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2004633 | TP for TR 37 716-31-11 to include DC_5A-12A-48A_n71A | Ericsson, US Cellular |
| R4-2004634 | TP for TR 37 716-31-11 to include DC_5A-12A-66A_n71A | Ericsson, US Cellular |
| R4-2004635 | TP for TR 37 716-31-11 to include DC_2A_5A-12A_n71A | Ericsson, US Cellular |
| R4-2005010 | TP to TR 37.716-31-11: Addition of DC_2A-5A_(n)12AA | Nokia, US Cellular |
| R4-2005011 | TP to TR 37.716-31-11: Addition of DC_2A-12A_(n)5AA | Nokia, US Cellular |
| R4-2005012 | TP to TR 37.716-31-11: Addition of DC_2A-48A_(n)5AA | Nokia, US Cellular |
| R4-2005013 | TP to TR 37.716-31-11: Addition of DC_2A-66A_(n)5AA | Nokia, US Cellular |
| R4-2005014 | TP to TR 37.716-31-11: Addition of DC_5A-48A_(n)12AA | Nokia, US Cellular |
| R4-2005015 | TP to TR 37.716-31-11: Addition of DC_5A-66A_(n)12AA | Nokia, US Cellular |
| R4-2005016 | TP to TR 37.716-31-11: Addition of DC_12A-48A_(n)5AA | Nokia, US Cellular |
| R4-2005017 | TP to TR 37.716-31-11: Addition of DC_12A-66A_(n)5AA | Nokia, US Cellular |
| 8.6.1 | Rapporteur Input (WID/TR/CR) [DC_R16_4BLTE_1BNR_5DL2UL-Core/Perf] | |
| R4-2004216 | Revised WID on Dual Connectivity (EN-DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) Rel-16 | Nokia, Nokia Shanghai Bell |
| R4-2004217 | CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 | Nokia, Nokia Shanghai Bell |
| R4-2004218 | draftTR 37.716-41-11 v0.8.0 | Nokia, Nokia Shanghai Bell |
| 8.6.2 | EN-DC without FR2 band [DC_R16_4BLTE_1BNR_5DL2UL-Core] | |
| R4-2004226 | TP for 37.716-41-11 to introduce DC_1-3-7-28_n40 | Nokia, Nokia Shanghai Bell |
| 8.7.1 | Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL2UL-Core/Per] | |
| R4-2003224 | TR 37.716-21-21 v0.10.0 update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 | LG Electronics France |
| R4-2003225 | Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) EN DC in Rel-16 | LG Electronics France |
| R4-2003227 | Introducing CR on new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 | LG Electronics France |
| 8.7.2 | EN-DC including NR inter CA without FR2 band [DC_R16_xBLTE_2BNR_yDL2UL-Core] | |
| R4-2003134 | TP for TR 37.716-21-21: DC_1A-18A_n3A-n77A | Samsung, KDDI |
| R4-2003135 | TP for TR 37.716-21-21: DC_1A-28A_n3A-n77A | Samsung, KDDI |
| R4-2003136 | TP for TR 37.716-21-21: DC_1A-41A_n3A-n77A and DC_1A-41C_n3A-n77A | Samsung, KDDI |
| R4-2003137 | TP for TR 37.716-21-21: DC_1A-41A_n3A-n78A and DC_1A-41C_n3A-n78A | Samsung, KDDI |
| R4-2003138 | TP for TR 37.716-21-21: DC_1A-41A_n28A-n77A and DC_1A-41C_n28A-n77A | Samsung, KDDI |
| R4-2003139 | TP for TR 37.716-21-21: DC_1A-41A_n28A-n78A and DC_1A-41C_n28A-n78A | Samsung, KDDI |
| R4-2003140 | TP for TR 37.716-21-21: DC_3A-41A_n28A-n77A and DC_3A-41C_n28A-n77A | Samsung, KDDI |
| R4-2003141 | TP for TR 37.716-21-21: DC_3A-41A_n28A-n78A and DC_3A-41C_n28A-n78A | Samsung, KDDI |
| R4-2003142 | TP for TR 37.716-21-21: DC_18A_n3A-n77A | Samsung, KDDI |
| R4-2003143 | TP for TR 37.716-21-21: DC_18A-41A_n3A-n77A and DC_18A-41C_n3A-n77A | Samsung, KDDI |
| R4-2003144 | TP for TR 37.716-21-21: DC_18A-41A_n3A-n78A and DC_18A-41C_n3A-n78A | Samsung, KDDI |
| R4-2003145 | TP for TR 37.716-21-21: DC_28A_n3A-n77A | Samsung, KDDI |
| R4-2003146 | TP for TR 37.716-21-21: DC_41_n3-n77 | Samsung, KDDI |
| R4-2003147 | TP for TR 37.716-21-21: DC_41_n3-n78 | Samsung, KDDI |
| R4-2003148 | TP for TR 37.716-21-21: DC_41_n28-n77 | Samsung, KDDI |
| R4-2003149 | TP for TR 37.716-21-21: DC_41_n28-n78 | Samsung, KDDI |
| R4-2003150 | TP for TR 37.716-21-21: DC_1-3-41_n28-n77 | Samsung, KDDI |
| R4-2003151 | TP for TR 37.716-21-21: DC_1-3-41_n28-n78 | Samsung, KDDI |
| R4-2003153 | TP for TR 37.716-21-21: DC_1-18-41_n3-n77 | Samsung, KDDI |
| R4-2003154 | TP for TR 37.716-21-21: DC_1-18-41_n3-n78 | Samsung, KDDI |
| R4-2003163 | TP for TR 37.716-21-21: DC_2A-7C_n66A-n78A | Samsung, Bell mobility |
| R4-2003164 | TP for TR 37.716-21-21: DC_2A-7C-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2003165 | TP for TR 37.716-21-21: DC_7C_n66A-n78A | Samsung, Bell mobility |
| R4-2003166 | TP for TR 37.716-21-21: DC_7C-66A_n66A-n78A | Samsung, Bell mobility |
| R4-2003228 | TP on summary of self-interference analysis for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 | LG Electronics France |
| R4-2003230 | MSD results for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 | LG Electronics France |
| R4-2003450 | TP for TR 37.716-21-21: EN-DC_1_n28-n77 | SoftBank Corp. |
| R4-2003453 | TP for TR 37.716-21-21: EN-DC_3_n28-n77 | SoftBank Corp. |
| R4-2003456 | TP for TR 37.716-21-21: EN-DC_8_n28-n77 | SoftBank Corp. |
| R4-2003507 | TP for TR 37.716-21-21: support of DC_3_n1-n257, DC_3-3_n1-n257, DC_7_n1-n257, DC_7-7_n1-n257 | CHTTL |
| R4-2003513 | TP for TR 37.716-21-21: support of DC_3-7_n1-n257, DC_3-3-7_n1-n257, DC_3-3-7_n1-n257, DC_3-3-7-7_n1-n257 | CHTTL |
| R4-2003585 | TP to TR 37.716-21-21 DC_20A_n78A-n92A | Huawei, HiSilicon |
| R4-2003793 | TP for TR37.716-21-21_ DC_8A_n40A-n41A | ZTE Corporation |
| R4-2003794 | TP for TR37.716-21-21_ DC_39A_n40A-n41A | ZTE Corporation |
| R4-2003795 | TP for TR37.716-21-21_ Updated DC_3A_n40A-n79A and DC_3A_n41A-n79A | ZTE Corporation |
| R4-2003796 | TP for TR37.716-21-21_ Updated DC_8A_n40A-n79A and DC_8A_n41A-n79A | ZTE Corporation |
| R4-2003797 | TP for TR37.716-21-21_ Updated DC_39A_n40A-n79A and DC_39A_n41A-n79A | ZTE Corporation |
| R4-2003940 | TP for TR 37.716-21-21: DC_1A_n41A-n78A | Huawei, HiSilicon,Etisalat |
| R4-2003941 | TP for TR 37.716-21-21: DC_3A_n41A-n78A | Huawei, HiSilicon,Etisalat |
| R4-2003942 | TP for TR 37.716-21-21: DC_20A_n41A-n78A | Huawei, HiSilicon,Etisalat |
| R4-2003943 | TP for TR 37.716-21-21: DC_20A_n75A-n78A\DC_20A_n75A-n78(2A) | Huawei, HiSilicon |
| R4-2003944 | draftCR for 38.101-3 to add missing configuration DC_3A_n20A-n78A | Huawei, HiSilicon |
| R4-2004065 | TP for 37.716-21-21 for DC_1A_n8A-n40A | Huawei Technologies R&D UK |
| R4-2004066 | TP for 37.716-21-21 for DC_1A_n40A-n78(2A) | Huawei, HiSilicon |
| R4-2004134 | TP for TR 37.716-21-21 DC_20A_n7A-n28A | Huawei, HiSilicon |
| R4-2004227 | TP for 37.716-21-21 to introduce DC_28_n40-n78 | Nokia, Nokia Shanghai Bell |
| R4-2004228 | TP for 37.716-21-21 to introduce DC-1-3_n40-n78 | Nokia, Nokia Shanghai Bell |
| R4-2004229 | TP for 37.716-21-21 to introduce DC-1-28_n40-n78 | Nokia, Nokia Shanghai Bell |
| R4-2004230 | TP for 37.716-21-21 to introduce DC-3-28_n40-n78 | Nokia, Nokia Shanghai Bell |
| R4-2004231 | TP for 37.716-21-21 to introduce DC-1-3-28_n40-n78 | Nokia, Nokia Shanghai Bell |
| R4-2004414 | Draft CR to TS 38.101-3 on delta TIB and RIB for xBLTE-2BNR (Rel-16) | ZTE Corporation |
| R4-2004508 | TP to TR 37.716-21-11: CA_3_n7-n28 | Nokia, Nokia, Shanghai Bell, BT plc |
| R4-2004509 | Draft CR to 38.101-3 to add 46-66_n25-n71 configurations | Nokia, Nokia Shanghai Bell, T-Mobile USA inc. |
| R4-2004510 | Draft CR to 38.101-3 to add 2-46_n66-n71 configurations | Nokia, Nokia Shanghai Bell, T-Mobile USA inc. |
| R4-2004511 | Draft CR to 38.101-3 to add 2-46_n41-n71 configurations | Nokia, Nokia Shanghai Bell, T-Mobile USA inc. |
| R4-2004512 | Draft CR to 38.101-3 to add 46-66_n41-n71 configurations | Nokia, Nokia Shanghai Bell, T-Mobile USA inc. |
| R4-2004598 | draft Rel-16 CR to 38.101-3 to add DC_3_n7-n78 configurations | Ericsson, Telstra |
| R4-2004599 | TP for TR 37.716-21-21 to include DC_1-7_n7-n78 | Ericsson, Telstra |
| R4-2004600 | TP for TR 37.716-21-21 to include DC_3-7_n7-n78 | Ericsson, Telstra |
| R4-2004601 | TP for TR 37.716-21-21 to include DC_7-28_n7-n78 | Ericsson, Telstra |
| R4-2004602 | TP for TR 37.716-21-21 to include DC_1-3-7_n7-n78 | Ericsson, Telstra |
| R4-2004603 | TP for TR 37.716-21-21 to include DC_1-7-28_n7-n78 | Ericsson, Telstra |
| R4-2004604 | TP for TR 37.716-21-21 to include DC_3-7-28_n7-n78 | Ericsson, Telstra |
| R4-2004605 | TP for TR 37.716-21-21 to include DC_1-3-7-28_n7-n78 | Ericsson, Telstra |
| R4-2004616 | TP for TR 37.716-21-21 to include DC_1A_n28A-n40A | Ericsson |
| R4-2004617 | TP for TR 37.716-21-21 to include DC_3A_n1A-n40A | Ericsson |
| R4-2004618 | TP for TR 37.716-21-21 to include DC_3A_n8A-n40A | Ericsson |
| R4-2004619 | TP for TR 37.716-21-21 to include DC_3A_n8A-n78A | Ericsson |
| R4-2004620 | TP for TR 37.716-21-21 to include DC_3A_n28A-n40A | Ericsson |
| R4-2004621 | TP for TR 37.716-21-21 to include DC_7A_n1A-n40A | Ericsson |
| R4-2004622 | TP for TR 37.716-21-21 to include DC_7A_n8A-n40A | Ericsson |
| R4-2004623 | TP for TR 37.716-21-21 to include DC_7A_n8A-n78A | Ericsson |
| R4-2004624 | TP for TR 37.716-21-21 to include DC_7A_n28A-n40A | Ericsson |
| 8.7.3 | EN-DC including NR inter CA with FR2 band | |
| R4-2003085 | Draft CR for TS38.101-3 on band combination for Inter-band EN-DC | Samsung, SK telecom |
| R4-2003152 | TP for TR 37.716-21-21: DC_1-3-41_n28-n257 | Samsung, KDDI |
| R4-2003155 | TP for TR 37.716-21-21: DC_1-18-41_n3-n257 | Samsung, KDDI |
| R4-2003156 | TP for TR 37.716-21-21: DC_1-41_n3-n257 | Samsung, KDDI |
| R4-2003442 | Draft CR for TS 38.101-3: Support of n77(2A) in DC_11_n77-n257 and DC_28_n77-n257 | SoftBank Corp. |
| R4-2003452 | TP for TR 37.716-21-21: EN-DC_1-11_n77-n257 | SoftBank Corp. |
| R4-2003455 | TP for TR 37.716-21-21: EN-DC_3-28_n77-n257 | SoftBank Corp. |
| R4-2003458 | TP for TR 37.716-21-21: EN-DC_8-11_n77-n257 | SoftBank Corp. |
| R4-2003716 | Draft CR for TS38.101-3 on band combination for Inter-band EN-DC | Samsung, SK telecom |
| R4-2003792 | TP for TR37.716-21-21_ DC_3A_n40A-n258A | ZTE Corporation |
| 8.8.1 | Rapporteur Input (WID/TR/CR) [NR_SUL_combos_R16-Core/Per] | |
| R4-2004135 | Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) | Huawei, HiSilicon |
| R4-2004136 | TR 37.716-00-00 v0.5.0 | Huawei, HiSilicon |
| R4-2004137 | TR 37.716-00-00 v0.6.0 | Huawei, HiSilicon |
| R4-2004138 | DraftCR on Introduction of completed SUL band combinations into TS 38.101-1 | Huawei, HiSilicon |
| 8.8.2 | UE RF [NR_SUL_combos_R16-Core] | |
| R4-2003579 | draftCR to 38307 on applicable SUL requirements | Huawei, HiSilicon |
| R4-2003580 | draftCR to 38101-1 on CA_n78(2A)_SUL_n78A-n86A | Huawei, HiSilicon |
| R4-2004139 | Updated TP for TR 37.716-00-00: to clean up | Huawei, HiSilicon |
| R4-2004140 | Draft CR for 38.101-3: to clean up for SUL band combinations | Huawei, HiSilicon |
| R4-2004961 | TP for TR 37.716-00-00 for SUL_n41A-n95A | CMCC,Huawei, HiSilicon |
| R4-2004962 | TP for TR 37.716-00-00 for SUL_n79A-n95A | CMCC,Huawei, HiSilicon |
| 8.9.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_3BDL_1BUL-Core/Per] | |
| R4-2003317 | TR 38.716-03-01 v 0.2.0 | CATT |
| R4-2003318 | Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 | CATT |
| R4-2003319 | Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 | CATT |
| R4-2003320 | Revised WID: Rel-16 NR inter-band CA for 3 bands DL with 1 band UL | CATT |
| 8.9.2 | UE RF [NR_CA_R16_3BDL_1BUL-Core] | |
| R4-2003443 | Draft CR for TS 38.101-1: Support of n78(2A) in CA_n3-n28-n78 | SoftBank Corp. |
| R4-2003946 | TP for TR 38.716-03-01: CA_n28A-n41A-n78A | Huawei, HiSilicon,Etisalat |
| R4-2004625 | TP for TR 38.716-03-01 to include CA_n1A-n40A-n78A | Ericsson |
| R4-2004626 | TP for TR 38.716-03-01 to include CA_n28A-n40A-n78A | Ericsson |
| R4-2005018 | TP to TR 38.716-03-01: CA_n25-n66-n71 | Nokia, TMO US |
| R4-2005019 | TP to TR 38.716-03-01: CA_n25-n41-n66 | Nokia, TMO US |
| 8.10.1 | Rapporteur Input (WID/TR/CR) [NR_CA_R16_4BDL_1BUL-Core/Per] | |
| R4-2004570 | Revised WID 4 bands NR CA Rel-16 | Ericsson |
| R4-2004578 | TR 38.716-04-01 v0.3.0 Rel-16 NR Inter-band 4 bands CA | Ericsson |
| R4-2004581 | TP for TR 38.716-04-01 for updated scope from RAN #87 | Ericsson |
| R4-2004586 | draft CR introduction completed band combinations 38.716-04-01 -> 38.101-1 | Ericsson |
| R4-2004587 | draft CR introduction completed band combinations 38.716-04-01 -> 38.101-3 | Ericsson |
| 8.10.2 | UE RF [NR_CA_R16_4BDL_1BUL-Core] | |
| R4-2004072 | TP to TR 38.716-04-01 for CA_n7-n25-n66-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| 8.11.1 | Rapporteur Input (WID/TR/CR) [NR_CADC_R16_3BDL_2BUL-Core/Per] | |
| R4-2003952 | TR 38.716-03-02 v050 | ZTE Wistron Telecom AB |
| R4-2004179 | draftCR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-1 | ZTE Trunking Technology Corp. |
| R4-2004180 | draftCR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-3 | ZTE Trunking Technology Corp. |
| R4-2004181 | Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL | ZTE Trunking Technology Corp. |
| 8.11.2 | UE RF [NR_CADC_R16_3BDL_2BUL-Core] | |
| R4-2003162 | TP for TR 38.716-03-02: CA_n3A-n28A-n78A | Samsung, KDDI |
| R4-2003171 | Draft CR for 38.101-3 to introduce new inter band NR DC for 3BDL with 2BUL between FR1 and FR2 | Samsung, KDDI |
| R4-2003460 | TP update for TR 38.716-03-02: CA_n3-n28-n77 | SoftBank Corp. |
| R4-2004069 | TP to TR 38.716-03-02 for CA_n7-n25-n66 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004070 | TP to TR 38.716-03-02 for CA_n7-n66-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004071 | TP to TR 38.716-03-02 for CA_n25-n66-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| 8.12.1 | Rapporteur Input (WID/TR/CR) [DC_R16_LTE_NR_3DL3UL-Core/Per] | |
| R4-2003801 | Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL | ZTE Corporation |
| R4-2003802 | Draft CR to reflect the completed ENDC combinations for 3 bands DL with 3 bands UL into Rel16 TS 38.101-3 | ZTE Corporation |
| R4-2003803 | TR 37.716-33 v0.2.0: Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL | ZTE Corporation |
| 8.13.1 | Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL3UL-Core/Per] | |
| R4-2003882 | Revised WID Dual Connectivity (EN-DC) of LTE inter-band CA xDL1UL bands (x=2,3,4) and NR FR1 1DL1UL band and NR FR2 1DL1UL band | NTT DOCOMO INC. |
| R4-2003883 | Updated TR 37.716-41-22v0.1.0 | NTT DOCOMO INC. |
| R4-2003884 | draft CR for introduce new EN-DC of LTE 2,3,4 band + NR FR1 1UL/1DL band + NR FR2 1UL/1DL band for TS 38.101-3 | NTT DOCOMO INC. |
| 8.14.2 | UE RF (36.101, 38.101-1, 38.101-3) [LTE_NR_B41_Bn41_PC29dBm] | |
| R4-2003247 | A-MPR for PC1.5 intra-band EN-DC | LG Electronics Polska |
| R4-2004466 | Measurements for 29 dBm UL-MIMO MPR | T-Mobile USA Inc. |
| R4-2004637 | Architecture options for Rel-15 intra-band EN-DC PC2 and for Rel-16 PC1.5 | T-Mobile USA Inc., CMCC, Qorvo, Apple, Interdigital, Nokia, Skyworks Solutions, Inc., Intel, Motorola Mobility, Ericsson |
| R4-2004638 | 29 dBm HPUE IBE and EVM | T-Mobile USA Inc. |
| R4-2004639 | Proposal for measurement and simulation assumptions for 29 dBm UL MIIMO and Tx diversity MPR and A-MPR | T-Mobile USA Inc. |
| R4-2004689 | A-MPR Proposal for B41/n41 EN-DC | Apple Inc. |
| R4-2004690 | Clarification for PC1.5 intra-band EN-DC discussion | Apple Inc. |
| R4-2004815 | RIMD issues with two transmitters in PC1.5 | Qualcomm Incorporated |
| R4-2004963 | Draft CR_for Alloc_aware_ENDC_MPR for 38.101-3 | CMCC |
| 8.15 | Power Class 2 UE for EN-DC (1 LTE FDD band +1 NR TDD band) [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2003384 | Discussion on remaining issues for PC2 FDD+TDD HPUE | China Unicom |
| R4-2003385 | Discussion on remaining issues for PC2 FDD+TDD HPUE | China Unicom |
| R4-2003386 | Discussion on remaining issues for PC2 FDD+TDD HPUE | China Unicom |
| R4-2003387 | Discussion on remaining issues for PC2 FDD+TDD HPUE | China Unicom |
| R4-2003388 | Discussion on remaining issues for PC2 FDD+TDD HPUE | China Unicom |
| 8.15.1 | General [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2003514 | Discussion on the behaviors for FDD-TDD EN-DC High Power UE | CHTTL |
| R4-2003661 | Discussion on the remain issues for NSA high power UE | Xiaomi |
| R4-2004052 | CR for adding SAR solutions for FDD+TDD EN-DC PC2 UE | vivo |
| 8.15.2 | UE RF requirement [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2003086 | Further discussion on power class 2 UE for EN-DC FDD-TDD | Samsung |
| R4-2003878 | EN-DC Power Class 2 for FDD-TDD band combinations with and without tight CG coordination | Ericsson |
| R4-2003879 | Introduction of EN-DC power class 2 for FDD-TDD band combinations | Ericsson |
| R4-2004971 | Draft CR for adding power class 2 output power requirement for DC_3A_n41A | CMCC |
| 8.15.3 | Signaling [ENDC_UE_PC2_FDD_TDD-Core] | |
| R4-2003913 | Further on NSA FDD TDD HPUE | OPPO |
| R4-2004050 | On EN-DC (FDD+TDD) HPUE fall back schemes | vivo |
| R4-2004051 | Draft LS on UE capability for PC2 inter-band EN-DC (LTE FDD+NR TDD) | vivo |
| 8.16.1 | UE RF (38.101-2) [NR_n259-Core] | |
| R4-2003177 | Towards completion of n259 UE RF requirements | NTT DOCOMO, INC. |
| R4-2003178 | Draft CR for the introduction of n259 | NTT DOCOMO, INC. |
| R4-2004703 | Multi-band relaxaton framework for band n259 | Apple Inc. |
| R4-2004749 | On remaining UE RF requirements for n259 | Huawei, HiSilicon |
| R4-2004877 | dCR to 38.101-2: Incorporation of WRC19 Resolutions into n259 | Qualcomm Incorporated |
| 8.17.1 | UE RF (38.101-1) [NR_n1_BW2-Core] | |
| R4-2004493 | A-MPR simulation results for n1 50MHz | Huawei, HiSilicon |
| R4-2004692 | AMPR for n1 with 50MHz | Apple Inc. |
| R4-2004818 | n1 50MHz REFSENS and Band n34 Protection Measurements | Skyworks Solutions Inc. |
| 8.18.2 | Channel raster, sync raster, and UL shift [NR_n48_LTE_48_coex-Core] | |
| R4-2003175 | DSS in LTE/NR band 48/n48 | Samsung |
| R4-2003212 | On LTE/NR dynamic spectrum sharing for band 48/n48 | Intel Corporation |
| R4-2003336 | LTE/NR spectrum sharing in band 48/n48 | Ericsson |
| R4-2003462 | Study of DSS in band 48/n48 channel raster | CableLabs |
| R4-2003464 | Summary of channel raster analysis in DSS (band 48/n48) | CableLabs |
| R4-2004396 | Views on dynamic spectrum sharing between LTE band 48 and NR band n48 | Google Inc. |
| R4-2004507 | Views on band 48/n48 spectrum sharing | Nokia, Nokia Shanghai Bell |
| R4-2004515 | WF on offsetToCarrier clarification | CableLabs |
| R4-2004686 | LTE/NR spectrum sharing in band 48/n48 frequency range | Apple Inc. |
| R4-2004687 | LTE/NR spectrum sharing in band 48/n48 frequency range (UL shift) | Apple Inc., Comcast |
| 8.19.1 | UE RF (38.101-1) [NR_n3_BW] | |
| R4-2004125 | Band n3 - 40 MHz CBW – UE REFSENS requirements | Ericsson |
| R4-2004819 | n3 40MHz REFSENS Measurements | Skyworks Solutions Inc. |
| 6.15.1.10 | Inter-band CA requirement for FR2 UE measurement capability of independent Rx beam and/or common beam [NR_RRM_Enh_Core] | |
| R4-2003109 | RRM requirements for interband FR2 operation | Ericsson |
| R4-2003490 | Discussion on inter-band CA requirement for FR2 | NTT DOCOMO, INC. |
| R4-2003624 | Discussion on Inter-band CA requirement for FR2 | MediaTek inc. |
| R4-2004328 | Discussion on RRM requirements of FR2 inter-band CA scenario | Huawei, HiSilicon |
| R4-2004329 | DraftCR on scaling factor CSSFoutside_gap for FR2 inter-band CA | Huawei, HiSilicon |
| R4-2004330 | DraftCR on scheduling availability requirements for FR2 inter-band CA | Huawei, HiSilicon |
| R4-2004790 | RRM requirements with common and independent beams in FR2 | Qualcomm Incorporated |
| 8.20.1 | UE RF (38.101-1) | |
| R4-2004126 | Band n65 - Adding Channel BW - UE RF A-MPR | Ericsson |
| R4-2004693 | AMPR for n65 with 50MHz | Apple Inc. |
| R4-2004817 | [NR_n65_BW] Back-off measurements for 50MHz QPSK waveforms | Skyworks Solutions Inc. |
| 8.21 | Closed Rel-16 NR spectrum related WIs [WI code] | |
| R4-2003590 | Work Item Summary for introduction of variable duplex FDD bands | Huawei, HiSilicon |
| 8.21.1 | UE RF [WI code] | |
| R4-2003587 | draftCR on default AMPR singaling for variable duplex FDD bands | Huawei, HiSilicon |
| R4-2003588 | Discussion on the uplink sharing capability for variable duplex FDD bands | Huawei, HiSilicon |
| R4-2003589 | LS on the uplink sharing capability for variable duplex FDD bands | Huawei, HiSilicon |
| R4-2004416 | CR for n26 AMPR for 256QAM | Qualcomm Incorporated |
| 9.1.1 | General [FS_NR_MIMO_OTA_test] | |
| R4-2003639 | TP to TR 38.827 v1.2.0 on general part | CAICT |
| R4-2003640 | TR38.827 v1.3.0 NR MIMO OTA | CAICT |
| 9.1.2 | Performance metrics [FS_NR_MIMO_OTA_test] | |
| R4-2003914 | Consideration on performance metrics Option 1 | OPPO |
| R4-2004995 | On FR2 performance metric and SNR range | Samsung |
| 9.1.3.1 | FR1 test methodologies [FS_NR_MIMO_OTA_test] | |
| R4-2003949 | FR1 MIMO OTA channel model validation methods | Huawei, HiSilicon |
| 9.1.3.2 | FR2 test methodologies [FS_NR_MIMO_OTA_test] | |
| R4-2003765 | Probe Layout for FR2 3D MPAC System | CAICT |
| R4-2003836 | Dynamic Geometry-based MIMO Throughput OTA Testing | Qualcomm Incorporated |
| R4-2003837 | Considerations on remaining issues for FR2 static MIMO OTA | Qualcomm Incorporated |
| R4-2004382 | System layout analysis and proposal for NR FR2 MIMO OTA | ROHDE & SCHWARZ |
| R4-2004384 | IFF based system for NR FR2 MIMO OTA | ROHDE & SCHWARZ |
| R4-2004386 | TP to TR 38.827 to introduce probe layout and IFF based system | ROHDE & SCHWARZ |
| R4-2004388 | TP to TR 38.827 to introduce PSP validation MU | ROHDE & SCHWARZ |
| R4-2004389 | Discussion on Dynamic Geometry for NR FR2 MIMO OTA | ROHDE & SCHWARZ |
| R4-2004564 | TP to TR38.827: FR2 3D MPAC Probe Configuration | Keysight Technologies UK Ltd, Spirent Communications |
| R4-2004565 | FR2 MIMO OTA channel model PSP validation | Keysight Technologies UK Ltd |
| R4-2004566 | System Implementation of FR2 3D MPAC Systems | Keysight Technologies UK Ltd |
| R4-2004718 | 3D MPAC Probe Configuration Proposal | Spirent Communications, Keysight Technologies UK Ltd |
| R4-2004889 | Dynamic geometry-based MIMO OTA Testing | Qualcomm Incorporated |
| 9.2.1 | General [FS_7to24GHz_NR] | |
| R4-2004013 | TR 38.820 v1.2.0 | Huawei Technologies Sweden AB |
| 9.2.2 | Regulatory survey [FS_7to24GHz_NR] | |
| R4-2004196 | TP to TR 38.820: Updates to the list of frequency ranges of interest | Huawei |
| 9.2.4 | RF technology aspects [FS_7to24GHz_NR] | |
| R4-2003756 | TP to TR 38.820: Improvement of technical background for phase noise characteristics in subclause 5.5.3 and Annex B | Ericsson |
| R4-2004197 | TP to TR 38.820: Updates to the PA survey | Huawei |
| 9.2.6.1 | BS types, BS requirement sets [FS_7to24GHz_NR] | |
| R4-2004950 | TP to TR 38.820: BS classes for 7-24 GHz frequency range | Nokia, Nokia Shanghai Bell |
| 9.2.6.3 | TX requirements | |
| R4-2004499 | TP to TR 38.820: ACS | Huawei |
| 9.2.6.4 | RX requirements | |
| R4-2004680 | TP to TR 38.820: Rx IMD | Huawei Tech.(UK) Co., Ltd |
| 10.1.1 | UE RF (38.101-2) [NR_FR2_FWA_Bn257_Bn258] | |
| R4-2003087 | Discussion on FR2 FWA UE with maximum TRP of 23dBm | Samsung |
| R4-2003345 | New FR2 FWA with 23dBm max TRP | Intel Corporation |
| R4-2003417 | On power class definition for FR2 FWA UE | Ericsson |
| R4-2003535 | Minimum peak EIRP and REFSENS link budgets for new FR2 FWA UE | MediaTek Inc. |
| R4-2003969 | Discussion on how to specify the new FR2 FWA UE with maximum TRP of 23dBm | KDDI Corporation |
| R4-2004429 | How to introduce FR2 new power class feature | NTT DOCOMO INC. |
| R4-2004506 | Views on FR2 FWA UE with maximum TRP of 23dBm for band n257 and n258 | Nokia, Nokia Shanghai Bell |
| R4-2004778 | on new FR2 FWA UE requirement | Huawei, HiSilicon |
| R4-2004779 | on new FR2 FWA UE capability addresing for new UE RF requirement | Huawei, HiSilicon |
| R4-2004780 | on beam correspondence requirement for new FR2 FWA UE | Huawei, HiSilicon |
| R4-2004865 | FR2 23dBm FWA Discussion | Qualcomm Incorporated |
| 10.1.3 | RRM (38.133) [NR_FR2_FWA_Bn257_Bn258] | |
| R4-2004376 | Initial discussion on RRM impact due to introduction of new FR2 FWA UE | Huawei, HiSilicon |
| 10.1.4 | Others [NR_FR2_FWA_Bn257_Bn258] | |
| R4-2003461 | Work plan for introducing FR2 FWA UE with maximum TRP of 23dBm for band n257 and n258 | SoftBank Corp. |
| 10.2 | Introduction of NR band n13 [NR_n13] | |
| R4-2004482 | Work plan on introduction of NR band n13 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2004483 | System parameters for NR band n13 | Huawei, HiSilicon, Bell Mobility, Telus |
| 10.2.1 | UE RF (38.101-1) [NR_n13-Core] | |
| R4-2004464 | n13 Requirements | Qualcomm Incorporated |
| R4-2004484 | UE additional emission limits | Huawei, HiSilicon, Bell Mobility, Telus |
| 11.1 | Study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz [FS_6425_10500MHz _NR] | |
| R4-2004127 | SI on IMT parameters - Work Plan | Ericsson |
| R4-2004128 | SI on IMT parameters - simulation assumptions | Ericsson |
| R4-2004129 | SI on IMT parameters - Common parameters for 6.425-7.025GHz / 7.025-7.125 / 10.0 – 10.5 GHz | Ericsson |
| R4-2004477 | TR Skeleton on parameters for IMT studies on 6.425-7.025GHz, 7.025-7.125GHz and 10.0-10.5 GHz | Huawei, HiSilicon |
| R4-2004951 | System level simulation methodology and assumptions for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz | Nokia, Nokia Shanghai Bell |
| 11.1.1 | UE parameters | |
| R4-2004131 | SI on IMT parameters - UE parameters for 6.425-7.025GHz / 7.025-7.125 / 10.0 – 10.5 GHz | Ericsson |
| R4-2004479 | UE IMT technology related parameters for 6.425-7.025GHz and 7.025-7.125GHz | Huawei, HiSilicon |
| R4-2004481 | UE IMT technology related parameters for 10.0-10.5GHz | Huawei, HiSilicon |
| R4-2004973 | discussion on IMT parameters for frequency ranges below 7.125GHz | CMCC |
| 11.1.2 | BS parameters | |
| R4-2003762 | On IMT antenna parameters relevant for 6 to 7 GHz | Ericsson |
| R4-2004130 | SI on IMT parameters - BS parameters for 6.425-7.025GHz / 7.025-7.125 / 10.0 – 10.5 GHz | Ericsson |
| R4-2004144 | Discussion on IMT parameters for 6.425-7.125GHz and 10-10.5GHz | ZTE Corporation |
| R4-2004478 | BS IMT technology related parameters for 6.425-7.025GHz and 7.025-7.125GHz | Huawei, HiSilicon |
| R4-2004480 | BS IMT technology related parameters for 10.0-10.5GHz | Huawei, HiSilicon |
| R4-2004539 | IMT technology - 6.425-7.025GHz and 7.025-7.125GHz simulation parameters | Huawei |
| R4-2004540 | IMT technology 10-10.5 GHz simulation parameters | Huawei |
| 11.2 | Reply of IMT parameters for other frequency ranges requested in RP-200042 | |
| R4-2003322 | Reply LS on IMT-2020 parameters for sharing and compatibility studies for frequency for WRC23 | CATT |
| R4-2003323 | IMT parameters for the frequency ranges below 5 GHz | CATT |
| R4-2004541 | Reply of IMT parameters for other frequency ranges requested in RP-200042 | Huawei |
| R4-2004729 | Draft LS to Parameters of terrestrial component of IMT for sharing andcompatibility studies in preparation for WRC-23 (below 6 GHz) | Ericsson |
| R4-2004952 | Reply to ITU-R WP5D on IMT parameters for 470-4990 MHz | Nokia, Nokia Shanghai Bell |
| 12 | Liaison and output to other groups | |
| R4-2003399 | On secondary DRX group for FR1+FR2 CA | Apple |
| R4-2003400 | LS on secondary DRX group for FR1+FR2 CA | Apple |
| R4-2004189 | Discussions on RRM impact due to secondary DRX group | Ericsson |
| R4-2004190 | Reply LS on secondary DRX group | Ericsson |
| 13.1 | Simplification of band combinations in RAN4 specifications | |
| R4-2003880 | Further discussion on simplification of EN-DC configuration including FR2 | NTT DOCOMO INC. |
| R4-2003948 | Discussion on improvement of request, SR and BC basket WID index table | Huawei, HiSilicon |
| 13.2.2 | Proposals on adding “brand new” channel bandwidth | |
| R4-2003524 | Discussion on scalable solutions to handle brand new channel bandwidth | CMCC |
| R4-2003735 | Discussion on approaches for introduction of brand new channel bandwidths for NR | Huawei, HiSilicon |
| R4-2003736 | New WID proposal: introduction of brand new channel bandwidths for NR | Huawei, HiSilicon |
| R4-2004688 | Non-standard spectrum allocations for NR bands | Apple Inc. |
| 13.2.3 | Basket WIs for LTE CA, EN-DC, NR CA and NR DC | |
| R4-2003176 | Proposal on new Rel-17 Basket: NR inter-band Carrier Aggregation and Dual connectivity for DL 4 bands and 2UL bands | Samsung |
| R4-2003324 | Motivation on basket WI on V2X band combination | CATT |
| R4-2003325 | New basket WID: V2X band combination for supporting co-current operation between Uu frequency bands and V2X bands | CATT |
| R4-2003391 | New WID: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5) with 1 band UL | Nokia, Nokia Shanghai Bell |
| R4-2003660 | New WID on Power Class 2 UE for NR inter-band CA and SUL band combination with 2 bands UL | China Telecom |
| R4-2003790 | New WID: EN-DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) | ZTE Corporation |
| R4-2004571 | New WID Basket WI for LTE Intra-band CA Rel-17 | Ericsson |
| R4-2004572 | New WID NR Intra-band Rel-17 | Ericsson |
| R4-2004573 | New WID LTE 3DL and one NR band Rel-17 | Ericsson |
| R4-2004574 | New WID 4 bands NR CA Rel-17 | Ericsson |
| 13.2.4 | Others | |
| R4-2003199 | Motivation to introduce new SI of MG enhancement | Intel Corporation, Apple |
| R4-2003200 | New SI Proposal Study on measurement gap enhancement | Intel Corporation, Apple |
| R4-2003266 | Motivation on NR RRM requirement enhancement in Rel-17 | CATT |
| R4-2003267 | New WID on NR RRM requirement enhancement in Rel-17 | CATT |
| R4-2003406 | Motivation paper on Rel-17 further RRM enhancement | Apple |
| R4-2003506 | Motivation paper on R17 RRM enh | MediaTek inc. |
| R4-2003637 | New WID on Verification of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of NR UEs | CAICT |
| R4-2003638 | Motivation for WI: Verification of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of NR UEs | CAICT |
| R4-2003727 | New WID on UE performance for advanced recevier with soft IC for inter-stream interference and IRC for inter-cell interference | Huawei, HiSilicon |
| R4-2003728 | Motivation paper of new WID on UE performance for advanced recevier with soft IC for inter-stream interference and IRC for inter-cell interference | Huawei, HiSilicon |
| R4-2003737 | New WID proposal: supporting overlapping CA for LTE | Huawei, HiSilicon |
| R4-2003738 | Motivation on WID of further enhancement of FR1 RF requirement | Huawei, HiSilicon |
| R4-2003915 | New SID on NR FR1 and EN-DC FR1 UE TRP and TRS | OPPO |
| R4-2003916 | Motivation of NR FR1 TRP TRS new study item | OPPO |
| R4-2004053 | Consideration on NR SISO OTA WI | vivo |
| R4-2004054 | Motivation for NR FR1 UE TRP and TRS | vivo, CMCC, CAICT, Rohde & Schwarz |
| R4-2004055 | New WID: NR FR1 UE SA and EN-DC TRP and TRS | vivo, CMCC, CAICT, Rohde & Schwarz |
| R4-2004461 | New SID on high-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12 and in Band 5 | US Cellular Corporation |
| R4-2004648 | Further discussion on linear method for power class fall back optimization | vivo |
| R4-2004649 | [draft] New SID: Optimizations on power class fall back | vivo |
| R4-2004716 | Views on NR FR1 TRP/TRS | Apple Inc. |
| R4-2004717 | FR2 RF enhancements for Rel-17 | Apple Inc. |
| R4-2004906 | Motivation for further enhancement on NR demodulation performance requirements | China Telecom |
| R4-2004907 | Draft WID: Further enhancement on NR demodulation performance requirements | China Telecom |
| R4-2004965 | Motivation for new WI on air-to-ground network for NR | CMCC |
| R4-2004966 | New WID on air-to-ground network for NR | CMCC |
| R4-2004967 | New WID on introduction of 1880-1920MHz SUL band for NR | CMCC |
| 13.3 | Others | |
| R4-2003739 | Re-consideration of adding UE 100MHz channel bandwidth for n40 | Huawei, HiSilicon |
| 14 | Any other business | |
| R4-2003723 | Discsussion on LTE CQI reporting cases with same MCS value | Huawei, HiSilicon |
| R4-2003724 | draftCR: Updates to LTE test cases 9.2.1.7 and 9.2.1.8 (Rel-12) | Huawei, HiSilicon |
| R4-2003725 | Discussion on single carrier performance requirements for FDD CA with minimum channel spacing | Huawei, HiSilicon |
| R4-2003726 | draftCR: Introduction for intra-band contiguous CA performance requirements for FDD with minimum channel spacing | Huawei, HiSilicon |
| R4-2004825 | Maintaining 38.101 Specification quality when introducing new sections | Qualcomm Incorporated |